jasonbrimhall.info Report : Visit Site

Technical data of the jasonbrimhall.info

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host jasonbrimhall.info. Currently, hosted in United States and its service provider is GoDaddy.com LLC .

the related websites

amazon.co.uk foyles.co.uk topsqlblogs.com rd.springer.com bookdepository.com link.springer.com books.telegraph.co.uk barnesandnoble.com 

HTTP Header Analysis

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

DNS

HtmlToText

sql rnnr 1 dba's professional blog home book reviews running blogging about home quickly change sql job owners by jason brimhall categories: news , professional , sqlserverpedia syndication , ssc tags: agent job , back to basics , sql administration , sql agent , sql internals , sql server comments: 3 comments published on: july 16, 2018 it is not unusual to find a server where some random user created a bunch of jobs to be run by sql agent. sometimes, the user creating the job(s) sets themself as the owner of the job. there are certain cases where this behavior is hard to avoid like when creating a maintenance plan . and of course, there are times when the user just doesn’t know any better. there is of course, the rare occasion when setting the job owner to be ones self makes the most sense -but that is few and far between in the grand scheme. usually, you will want a non-expiring account such as a service account or a principal without “logon” permissions to be the owner. the primary reason being simple – humans have an expiration date for every job they will ever have. when that expiration occurs, you may end up with any number of unwanted side effects. unwanted side effects is exactly what we try to avoid in our jobs run via sql agent. no expiration date there are two basic means to change the owner of every job on your server. either you open each job one by one and set the owner to an acceptable principal. this method is rather tedious and you will be fighting off the boredom if you have a few hundred jobs on the server. or, the alternative, change the job owners group by group (set-based theory). this second method can be far less tedious and far more efficient. the second method is by far my preferred method. let’s take a look at how to make all of these changes in groups. job owners transact-sql use msdb; go declare @ownerchangefrom varchar(256) = 'mydomain\gomer.clown' , @ownerchangeto varchar(256) = 'sa' , @ownersidchangeto varbinary(85); select @ownersidchangeto = sp.sid from sys.server_principals sp where sp.name = @ownerchangeto; begin tran; select j.name as jobname , sc.name as categoryname , isnull(sp.name, suser_sname(j.owner_sid)) as ownername , j.owner_sid , j.date_created from dbo.sysjobs j left outer join sys.server_principals sp on j.owner_sid = sp.sid inner join syscategories sc on j.category_id = sc.category_id where j.owner_sid = suser_sid(@ownerchangefrom); update j set owner_sid = @ownersidchangeto from dbo.sysjobs j left outer join sys.server_principals sp on j.owner_sid = sp.sid inner join syscategories sc on j.category_id = sc.category_id where sp.name = @ownerchangefrom --or sp.name is null or j.owner_sid = suser_sid(@ownerchangefrom); select j.name as jobname , sc.name as categoryname , sp.name as ownername , j.owner_sid , j.date_created from dbo.sysjobs j inner join sys.server_principals sp on j.owner_sid = sp.sid inner join syscategories sc on j.category_id = sc.category_id; --rollback transaction; --commit transaction; 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 use msdb ; go declare @ ownerchangefrom varchar ( 256 ) = 'mydomain\gomer.clown' , @ ownerchangeto varchar ( 256 ) = 'sa' , @ ownersidchangeto varbinary ( 85 ) ; select @ ownersidchangeto = sp . sid from sys . server_principals sp where sp . name = @ ownerchangeto ; begin tran ; select j . name as jobname , sc . name as categoryname , isnull ( sp . name , suser_sname ( j . owner_sid ) ) as ownername , j . owner_sid , j . date_created from dbo . sysjobs j left outer join sys . server_principals sp on j . owner_sid = sp . sid inner join syscategories sc on j . category_id = sc . category_id where j . owner_sid = suser_sid ( @ ownerchangefrom ) ; update j set owner_sid = @ ownersidchangeto from dbo . sysjobs j left outer join sys . server_principals sp on j . owner_sid = sp . sid inner join syscategories sc on j . category_id = sc . category_id where sp . name = @ ownerchangefrom --or sp.name is null or j . owner_sid = suser_sid ( @ ownerchangefrom ) ; select j . name as jobname , sc . name as categoryname , sp . name as ownername , j . owner_sid , j . date_created from dbo . sysjobs j inner join sys . server_principals sp on j . owner_sid = sp . sid inner join syscategories sc on j . category_id = sc . category_id ; --rollback transaction; --commit transaction; there are three basic sections to this script. first i fetch what should be changed, then i make the change, and lastly i verify the change. if the change doesn’t look right, then i can rollback the change. if the change is what i expected, then i can commit the change. those are the broad strokes. at a more detailed glimpse, i have setup a few variables to compare what i want to change, what the new job owner should be and then i fetch the sid of that new job owner. in my example, i am setting everything to ‘sa’. why? because it is easy for the sake of the example in the article – nothing more! since sometimes the owner of the job may only have access to the sql instance via a domain group, i also take advantage of a couple of functions to double check that it is the correct account. these functions i am using are suser_sid() and suser_sname() . when all is done as i am expecting, then i should see something similar to the following. since the change is what i expect, then at this point i would proceed with the commit transaction statement. the wrap as you can see, making job ownership changes at group scale instead of one by one is pretty easy. this only takes a matter of seconds to run against hundreds of jobs. that same kind of task done one at a time could easily take more than 40 minutes. i am not sure i want to spend that much time on such an innocuous task. i hope you are now able to use what you have learned to improve your skills and become a rock-star dba. enjoy! if you feel the need to read more about single-user mode, here is an article and another on the topic. this has been another post in the back to basics series. other topics in the series include (but are not limited to): backups , backup history and user logins . t-sql tuesday #104: just can’t cut that cord by jason brimhall categories: news , professional , scripts , sqlbp , ssc , tsql tuesday tags: audit , community , sql administration , sql script , sqlfamily , tsql tuesday comments: 2 comments published on: july 10, 2018 we all have our favorite scripts, tools or utilities. those are the things that help make our jobs easier. some of us may have an unhealthy relationship with some of those scripts (similar in nature to the relationship many have with their phone). whether or not the need to cut that proverbial cord exists, today we are not discussing the health of that dependence. suffice it to say, sometimes we simply need to upgrade our scripts. how else can we get better scripts or make our scripts better – by sharing them. this is precisely the goal bert wagner ( b | t ) seems to have envisioned for the 104th installment of tsql tuesday. if you are interested in reading the original invite, you can find that here . “ for this month’s t-sql tuesday, i want you to write about code you’ve written that you would hate to live without. maybe you built a maintenance script to free up disk space, wrote a query to gather system stats for monitoring, or coded some powershell to clean up string data. your work doesn’t need to be completely original either – maybe you’ve improved the code in some open source project to better solve the problem for your particular situation.” there is a high probability that through the sharing of your script, somebody out there can benefit from that script. in addition, it is very likely that somebody will make a suggestion to help make your script better. worst case (emphasis on worst case here), you have the script stored somewhere with half decent instructions on what it does and making it easily accessible f

URL analysis for jasonbrimhall.info

http://jasonbrimhall.info/2017/10/30/whats-that-ssis-password/
http://jasonbrimhall.info/2018/06/28/use-ssms-with-a-different-windows-account-back-to-basics/#comment-298345
http://jasonbrimhall.info/index.php?now_reading_author=jason-brimhall-david-dye-jonathan-gennick-andy-roberts-wayne-sheffield
http://jasonbrimhall.info/2018/06/28/use-ssms-with-a-different-windows-account-back-to-basics/#comments
http://jasonbrimhall.info/2018/07/10/just-cant-cut-that-cord/
http://jasonbrimhall.info/2018/07/16/quickly-change-sql-job-owners/#comment-301736
http://jasonbrimhall.info/2015/09/08/learning-extended-events-in-60-days/
http://jasonbrimhall.info/index.php?now_reading_library=true
http://jasonbrimhall.info/2018/05/31/single-user-mode-back-to-basics/
http://jasonbrimhall.info/?s=audit
http://jasonbrimhall.info/author/admin/
http://jasonbrimhall.info/tag/back-to-basics/
http://jasonbrimhall.info/2014/10/08/october-2014-las-vegas-ug-meeting/
http://jasonbrimhall.info/2016/12/23/user-contains-invalid-characters-back-to-basics/
http://jasonbrimhall.info/2010/01/05/primary-key-discovery/

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: JASONBRIMHALL.INFO
Registry Domain ID: D30975960-LRMS
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2018-01-01T15:20:31Z
Creation Date: 2009-12-31T01:11:02Z
Registry Expiry Date: 2019-12-31T01:11:02Z
Registrar Registration Expiration Date:
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization:
Registrant State/Province: Utah
Registrant Country: US
Name Server: NS27.DOMAINCONTROL.COM
Name Server: NS28.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form is https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-05-01T08:54:41Z <<<

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

Access to AFILIAS WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Afilias registry database. The data in this record is provided by Afilias Limited for informational purposes only, and Afilias does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Afilias reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

  REFERRER http://whois.afilias.info

  REGISTRAR Afilias Global Registry Services

SERVERS

  SERVER info.whois-servers.net

  ARGS jasonbrimhall.info

  PORT 43

  TYPE domain

DOMAIN

  NAME jasonbrimhall.info

  HANDLE D30975960-LRMS

  CREATED 2009-12-31

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

NSERVER

  NS27.DOMAINCONTROL.COM 97.74.103.14

  NS28.DOMAINCONTROL.COM 173.201.71.14

OWNER

ADDRESS

  STATE Utah

  COUNTRY US

  REGISTERED yes

Mistakes

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