djheath.net Report : Visit Site

Technical data of the djheath.net

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host djheath.net. Currently, hosted in United Kingdom and its service provider is UK Webhosting Ltd .

the related websites

diynot.com 406oc.co.uk forums.moneysavingexpert.com 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called nginx containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

search: home about posts comments sharepoint workflows sql server administration security uncategorized identify the last full, log and differential backup date and times for each database. june 3, 2015 leave a comment the following script is very useful if you just want to find out when each database was last backed up. it returns the database name, it’s recovery type, (important so that missing log backups for simple recovery can be ignored), and the date and time of each full, log and differential backup. this query could be used in an agent job which could be scheduled to run each day and look for any databases that (a), haven’t had a full backup for more than a day and (b), any databases which are using the full recovery model, which haven’t had a transaction log backup for more than a day. select distinct d . database_id as database_id , d . name as database_name , d . recovery_model_desc , isnull ( convert ( varchar ( 25 ) , max ( f . backup_start_date ) over ( partition by f . database_name ) , 113 ) , ‘never’ ) as last_full_backup_date , case d . recovery_model_desc when ‘simple’ then ‘n/a’ else isnull ( convert ( varchar ( 25 ) , max ( l . backup_start_date ) over ( partition by l . database_name ) , 113 ) , ‘never’ ) end as last_log_backup_date , isnull ( convert ( varchar ( 25 ) , max ( i . backup_start_date ) over ( partition by i . database_name ) , 113 ) , ‘never’ ) as last_diff_backup_date from sys . databases d left outer join msdb . . backupset f on f . database_name = d . name and f . type = ‘d’ left outer join msdb . . backupset l on l . database_name = d . name and l . type = ‘l’ left outer join msdb . . backupset i on i . database_name = d . name and i . type = ‘i’ order by d . database_id ; advertisements filed under uncategorized never forget what that database is used for, with sql server extended properties! may 29, 2015 leave a comment when i create a new database, i always set the extended properties of the database so that i can record a few key pieces of information. this is really useful to be able to quickly identify what the database is used for, who the business owner is, the date it was created and any other information that may be valuable, but easily forgotten. there are numerous times people have asked me what the database is for such and such an application, especially when there are a few versions of the same software being used across the organisation and each one has its own database named slightly differently. you can see the extended properties of a database by right clicking on the database object in ssms and selecting ‘properties’. then select ‘extended properties’. i usually keep to the same format when recording property values, namely: a description of the database, including the application that uses it. the date it was created. the business owner, or team which supports the application. the server name of each server that connects to it. this is especially useful when the database has to be moved to a new or upgraded sql server and you need to know which servers have to have their connection strings changed. to fill in the extended property i run the following script on the database in question, adding in the values for each property type: use [] go exec sp_addextendedproperty @name = n’contact’ , @value = n” — example: accounts team, john smith exec sp_addextendedproperty @name = n’created’ , @value = n” — example: 01/01/2015 exec sp_addextendedproperty @name = n’description’ , @value = n” — example: used for payroll data, must be setup with full recovery. exec sp_addextendedproperty @name = n’applicationserver’ , @value = n” — example: appserver1, appserver15 go once the databases have had their properties set, you can then periodically run reports on them. this can be useful if you want to find out if a database is still used, but don’t know who the contact is or what the database is actually used for. to do this, the following script can be run to generate a report: — create a global tempory table to hold the results . create table ##results ( id int identity ( 1 , 1 ) , databasename varchar ( 50 ) , description varchar ( 250 ) , contact varchar ( 250 ) ); — this first command will simply add all databases to the table declare @command varchar ( 1000 ); insert into ##results ( databasename ) select name from sys . databases where name not in ( ‘master’ , ‘tempdb’ , ‘model’ , ‘msdn’ ); — build the update command to get the description and contact information for each database. select @command = ‘use [?] update ##results set description = convert(varchar(250), description.value), contact = convert(varchar(250), contact.value) from sys.extended_properties description, sys.extended_properties contact where description.class_desc =”database” and description.name = ”ms_description” and contact.class_desc =”database” and contact.name = ”ms_contact” and ##results.databasename = db_name(db_id()) ‘ ; — execute the command on each database exec sp_msforeachdb @command ; — select the results and drop the table select * from ##results order by databasename ; drop table ##results ; this results in the following output: what is also useful, is this report shows any databases that don’t have the properties set. this means you can run this periodically to make sure you keep the records updated. you can change the query used in the report to generate any information held in the extended properties. for more information on extended properties check out bol , or this blog post by glen berry which details the use of extended properties in great detail. filed under uncategorized identify the size and document count of a single sharepoint site december 17, 2013 leave a comment the following query is useful, if you have a sharepoint site which uses one content database and all websites hang off the one top url. the script can be used to identify the total size of each site and the number of documents contained in the site. use [<yourcontentdatabasename>]; — don’t forget the semi-colon! with folderhierachy as( select f.fullurl, (((sum(cast(d.size as bigint))) / 1024) /1024) as sizeinmb, count(d.id) as doccount from webs f, docs d, lists l where d.webid = f.id and l.tp_id = d.listid and d.size > 0 and (d.leafname not like ‘%.stp’) and (d.leafname not like ‘%.aspx’) and (d.leafname not like ‘%.xfp’) and (d.leafname not like ‘%.dwp’) and (d.leafname not like ‘%template%’) and (d.leafname not like ‘%.inf’) and (d.leafname not like ‘%.css’) group by f.fullurl ) select substring(fullurl,1,charindex(‘/’,fullurl)) as url, sum(sizeinmb) as “size in mb”, sum(doccount) as “document count” from folderhierachy group by substring(fullurl,1,charindex(‘/’,fullurl)) order by url, [size in mb] desc; filed under uncategorized tagged with sharepoint red gate sql monitor metric – new logins to the sysadmin role. november 6, 2013 leave a comment red gate sql monitor metric – new logins to the sysadmin role. another one of my sql monitor custom metrics has been published by red gate. this one generates an alert when the count of server principles who are added to the sysadmin server role changes. it is very useful when multiple members of an it team may have a dba support function and are inclined to simple add users with sysadmin roles. this metric can be used to alert when this happens so it can be checked and verified in case it causes a security risk. filed under administration , security , sql server weekly sql: filter on sp_who2 in a table. november 6, 2013 leave a comment this is a new section of my blog, where i plan to publish a sql script on a weekly basis. these will be scripts i either use on a daily basis or ones which i find particularly interesting and worth sharing. this week, the following script is really useful for finding out who is connected to a particular database. it uses the sp_who2 special procedure and allows the data to be filtered. i am not sure where i got this script from, but it is not mine, but i must use it every day: run this on the database you wish to query: declare @table table( spid int, status varchar(max), login varchar(max), hostname varchar(max), blkby varchar(max), dbname varchar(max), command varchar(max), cputime int, diskio int, lastbatch varchar(max), programname varchar(max), spid_1 int, requestid int ) insert into @table exec sp_who2 select * from @table where dbname = db_name(db_id()) you can add to the where clause to filter on the different columns. i also use this script if i am restoring a database and need to quickly kill of any users. by adding the following extra code after the above, it will generate a the kill commands which i can copy and paste to a new query window: –generate a kill script select ‘kill ‘ + cast(spid as varchar(3)) from @table where dbname = db_name(db_id()) filed under administration , sql server first redgate sql metric published november 5, 2013 leave a comment first redgate sql metric published a while ago, my first red gate sql metric was published for use with red gates excellent sql monitor software. this metric allows you to be alerted when a transaction log grows over a defined threshold. this can be particularly useful if a process is stopping the log from truncating or the transaction backups have not been running successfully. filed under administration , sql server tagged with redgate , sql metrics , sql monitor , sql server , transaction logs spn setup for double hop from client (ie) to iis 8 to sql server (2012) october 22, 2013 2 comments the following is the required steps to set up kerberos authentication for a client to sql server. this is a rough post, created purely for self reference. a lot of this work is talked about at the following location http://blogs.msdn.com/b/psssql/archive/2011/02/21/sharepoint-adventures-using-kerberos-with-the-report-server.aspx on iis: open iss manager and go to application pools. set the correct application pool to use a dedicated user – right click and slect advanced settings. change identity to the domain user required. if you’re not sure what application pool is the being used by the web app, stop them all and then start them individually, whilst refreshing the web app. when the correct one is used, the web app should work (somewhat!). next, go to the web application web site in iis manager. double click authentication and enable asp.net impersonation (right click and select enable). right click on windows authentication and enable too. right click on windows authentication and select advance settings and untick enable kernel-mode authentication. click ok then right click on windows authentication and select providers. add negotiate:kerberos from the available providers drop down list. make sure this is the top of the list of enabled providers, above negotiate. on a domain connected computer: add the spn’s: open a cmd window and add an spn for the service account that the web app is running under. this is the domain account you set for the application pool. this spn should be for http service for the url of the server. in this case below the server name: setspn -a http/webservername domain\domainuser i.e: setspn -a http/sgbb1234 contoso\webappserviceuser add the spn for the fully qualified domain name too, i.e.: setspn -a http/sgbb1234.contoso.uk.com contoso\webappserviceuser now check the spn is set for the sql server service account. this is the account the sql server is running under: setspn -l sqlserverserviceaccount if nothing is listed, then add the spn for the database instance using port number and instance name: setspn -a mssqlsvc/servernamefqn:portnumber domain\sqlserviceaccount setspn -a mssqlsvc/servernamefqn:instancename domain\sqlserviceaccount i.e.: setspn -a mssqlsvc/dbserver.contoso.uk.com:1453 contoso\account1 setspn -a mssqlsvc/dbserver.contoso.uk.com:instance1 contoso\account1 after you have setup the spn’s using the setspn commands for the instance and port of the sql server service account, run the command <code>dsacls “cn=<commonname>, ou=<organisationunit>, dc=<domaincomponent>” /g self:rpwp;”serviceprincipalname”</code> change the cn, ou and dc values to be appropriate for the service account. if you look at the setspn command for the service account, this will provide you with these values and so the whole string can be copied and pasted i.e. <code>dsacls “cn=account1,ou=service accounts, ou=administrative, ou=ho, dc=contoso,dc=ad,dc=contoso,dc=com” /g self:rpwp;”serviceprincipalname”</code> the dsacls command is part of the ad feature pack. you should see the command complete successfully. once all is done, run the command setspn -x to check for any duplicates. remove any duplicate spn’s from the incorrect location. you will then need to restart sql so that it can register the spn in ad. now setup delegation: once the spn’s are set then the delegation tab will be visible in ad for users: open ad users and computers and navigate to the domain user used to run the app pool web service. click on delegation tab and select trust this user for delegation any service, or to a specific service if more granulatrity required. do the same for the iis server in ad too. once all the above is complete, restart iis. on the client pc, make sure no kerberos tickets are cached and causing a incorrect response. do this by opening a cmd window and typing “klist purge”. it should say tickets cleared. now do a ctrl + f5 refresh in ie, and the kerberos authentication should work! hopefully that is it! filed under administration , security , sql server tagged with authentication , kerberos , spns ← older posts advertisements categories select category sharepoint workflows sql server administration security uncategorized recent posts identify the last full, log and differential backup date and times for each database. never forget what that database is used for, with sql server extended properties! identify the size and document count of a single sharepoint site red gate sql monitor metric – new logins to the sysadmin role. weekly sql: filter on sp_who2 in a table. archives june 2015 may 2015 december 2013 november 2013 october 2013 february 2011 october 2010 september 2010 blogroll documentation plugins suggest ideas support forum themes wordpress blog wordpress planet meta register log in wordpress xhtml blog at wordpress.com. create a free website or blog at wordpress.com. post to cancel privacy & cookies: this site uses cookies. by continuing to use this website, you agree to their use. to find out more, including how to control cookies, see here: cookie policy

URL analysis for djheath.net

https://djheath.wordpress.com/tag/kerberos/
https://djheath.wordpress.com/page/2/
https://djheath.wordpress.com/category/sharepoint/
https://djheath.wordpress.com/2013/11/06/weekly-sql-filter-on-sp_who2-in-a-table/
https://djheath.wordpress.com/2013/10/
https://djheath.wordpress.com/tag/sql-metrics/
https://djheath.wordpress.com/2013/12/
https://djheath.wordpress.com/2015/06/
https://djheath.wordpress.com/feed/
https://djheath.wordpress.com/tag/sql-server/
https://djheath.wordpress.com/2013/11/06/weekly-sql-filter-on-sp_who2-in-a-table/#respond
https://djheath.wordpress.com/tag/authentication/
https://djheath.wordpress.com/2010/09/
https://djheath.wordpress.com/tag/sharepoint/
https://djheath.wordpress.com/category/sharepoint/workflows/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: DJHEATH.NET
Registry Domain ID: 138502921_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucowsdomains.com
Updated Date: 2015-11-30T16:09:57Z
Creation Date: 2004-12-30T15:10:04Z
Registry Expiry Date: 2018-12-30T15:10:04Z
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS.SRV2.COM
Name Server: NS2.SRV2.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-10-23T11:10:37Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR Tucows Domains Inc.

SERVERS

  SERVER net.whois-servers.net

  ARGS domain =djheath.net

  PORT 43

  TYPE domain

DOMAIN

  NAME djheath.net

  CHANGED 2015-11-30

  CREATED 2004-12-30

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

NSERVER

  NS.SRV2.COM 188.65.118.219

  NS2.SRV2.COM 188.65.116.176

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .