Yeah, it looks like that is for standard users. He has a section in the procedure where he specifically looks at the SA / dbo relationship.

Glad you were able...

Check out this post[/url] on the msdn site. Does this answer the question?

From BOL:

Log shipping has the following requirements:

SQL Server 2005 Standard, SQL Server 2005 Workgroup, SQL Server 2005 Enterprise Edition, or a later version, must be installed on all server...

Why the second command? Curious.

Well, I would drop that subscription and try again. Might even want to script out the publication, drop it, recreate it and then re-add the subscription.

I have never seen...

Frank Carrelli (4/30/2009)

---

The Query Plan does look solid except for two Key Lookups on two different sub-select statements. They are not using the indexes we originally created for those select...

What does the history on the job look like? Ultimately that is what runs the snapshot process so, either the job is running over and over or it is somehow...

Is the snapshot agent running multiple times? If so, check the schedule on there and make sure that it is not misconfigured in some way.

Lowell (4/30/2009)

---

this is a common issue after upgrading;

you've got to update statistics and rebuild indexes after upgrading or restoring a database that came from a previous version in order...

Does the execution plan look solid and does the indexing etc look good. It may be that the optimizer can't find a good plan based on the indexes and stats...

I can't think of what there would be information kept in master about this being a clustered instance as that is done through windows and the binaries. So, the restore...

There are varying levels of DR that you can build and it sounds like you are going for the real basic version which is most likely fine for your company....

It seems like you would need to get the proper file name and then build that into your restore script dynamically. So, you could use the following script as a...

Thanks for the correction Grant, it is headeronly.

Greg - the log backup is set to NOINIT so, that is probably where the problem lies.

Are you appending the backup to a previously existing file? What do you see when you run RESTORE FILELISTONLY from disk = 'YourPath\YourFile'?