2015-08-07 (first published: 2012-06-20)
15,744 reads
2015-08-07 (first published: 2012-06-20)
15,744 reads
will create jobs script for backup or DR purposes to install on another server.
2012-01-18 (first published: 2011-12-15)
2,167 reads
This script lists the name, running and success status, last executed/currently executing step name, Average and Last duration, next run time and other related information about Jobs.
2012-10-10 (first published: 2011-11-02)
2,111 reads
I have several problems with my corporate network and therefore need to do all my backups locally, and to make matters worse, still use SQL Server 2005.
2011-10-17 (first published: 2011-09-30)
434 reads
2011-07-27
2,359 reads
Find all Job Parent/Child Relationships and related DTSConfig file locations for each step.
2013-12-05 (first published: 2011-03-02)
1,736 reads
I needed to run an ssis package / job on many dates that were not consistent and initially started creating dozens of job schedules before coming up with this idea...
2011-01-13 (first published: 2010-12-29)
1,257 reads
The system stored procedure sp_start_job is a very useful T-SQL command that starts a SQL Agent job. The problem with this is that it starts the job and it doesn't wait until the job is finished and sometimes I want to start a job and wait until the job is finished and move on to another job or task that depends on the result of the previous job.
2010-11-29
3,405 reads
With this view you can obtain last failed job steps without using visual interface.
2010-03-30 (first published: 2010-03-19)
2,364 reads
This script will break job schedules down into a readable format (msdb.dbo.sysschedules)
2010-01-06 (first published: 2009-12-16)
1,964 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers