I've done it and it works fine, all of the functionality of SQL logshipping is simple to create.

You just create a job to backup the translog to disk, then to...

You can logship using any edition of SQL, however you would have to cerate the scripts yourself to do it.

Once you bring up the database in standby mode on the...

Never had a problem with it, and I have used it extensively, although there are a couple of small pitfalls that you have to look out for when setting it up...

We have hundreds of procs and I wanted to avoid having to recode the entire group by going through with the nolock hint which is why I wanted to go...

Check BOL about severity levels. Severity level 0 for sure only writes to the SQL Error Log.

In Yukon there will be.

I've run a couple of tests and it seem to be working as it should.

Thanks.

In my experience I would not use RAID 5 for anything unless I had to (ie couldn't get the head guys to fork out the dollars).

It's somewhat more costly but...

I would also suggest changing the job to use the dts name rather than the dts guid.

It could be a case where you made a change to the dts after...

I would go with

BACKUP LOG MWR_LIVE_DB_INCR_TEST  WITH NO_LOG

GO

USE MWR_LIVE_DB_INCR_TEST

GO

DECLARE @FILENAME VARCHAR(200), @sql VARCHAR(1000)

SELECT @FILENAME = RTRIM(NAME) FROM SYSFILES WHERE GROUPID = 0

SET @sql = 'DBCC...

Oh that is more cunning than cunning. I like it.

Sorry I'm not clarifying this right.

You can create a stored proc that simply is an sp_start_job for the job that you want to execute. Granting the permissions for that user...

Job level permissions are created by restricting access to the procedure which will execute the job.

I would create a stored proc that will execute the job grant the appropriate permissions to execute the proc to the user and whenever the user wants to execute the...

quote:

---

You might write a small VBScript for DTS Load from SQL Server and Save to structured file and 2nd script for Load...