Hey Jeff,

Thanks for your reply. Funny you should ask that as I'm in the process of testing and verifying that information. Initial tests show marginal differences in times,...

Thanks very much for the replies. I've corrected the counter issue and will look the versions that Luis provided.

I solved my problem.

All of the objects where created in master because the very first statement in your script states "user master". That sets the database context on which database to use...

Right click on the table and and generate the select statement to a query window and then edit the 3 or 4 columns that require the replace function. You...

The only other thing that comes to mind is if you're using compressed backups on the 2008R2 and not on the SQL 2012 servers.

The "TO" should only exist on the 1st line.

Backup Database TEST to

disk = '',

disk = '',

You need to add exec(@sql). The listed code only prints the statement.

Just so I understand the scenario, you have the same processes running between 2 2008R2 servers and 2 2012 servers, where the source and target are the same database versions....

The LSN chain for log shipping is only broken if a log is lost or corrupt. There are other scenarios, but all would envolve using differential backups and mutliple...

using QUOTENAME() around the database name should correct your issue.

Both scenarios are valid as long as you have all of the log files. Full backups won't interfere with the LSN of the transaction log backups.

Backup the original database and restore it to a new name using the WITH MOVE syntax to change the data and log file names.

You have to recover the database to allow the upgrade to complete. You could however immediately set the database to read-only.

To my knowledge you can't change a password through the ODBC call. You have to either execute the sp_password stored procedure , pass the password API to an application...