Viewing 15 posts - 1 through 15 (of 62 total)
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,...
January 25, 2016 at 6:39 pm
Thanks very much for the replies. I've corrected the counter issue and will look the versions that Luis provided.
January 25, 2016 at 11:53 am
I solved my problem.
October 16, 2014 at 10:26 am
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...
July 9, 2013 at 12:23 pm
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...
June 20, 2013 at 11:07 am
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.
March 19, 2013 at 1:13 pm
The "TO" should only exist on the 1st line.
Backup Database TEST to
disk = '',
disk = '',
March 19, 2013 at 12:24 pm
You need to add exec(@sql). The listed code only prints the statement.
March 19, 2013 at 12:15 pm
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....
March 19, 2013 at 11:44 am
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...
March 2, 2013 at 5:50 am
using QUOTENAME() around the database name should correct your issue.
February 28, 2013 at 11:38 am
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.
February 28, 2013 at 10:53 am
Backup the original database and restore it to a new name using the WITH MOVE syntax to change the data and log file names.
November 26, 2012 at 2:11 pm
You have to recover the database to allow the upgrade to complete. You could however immediately set the database to read-only.
November 12, 2012 at 1:29 pm
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...
November 12, 2012 at 12:49 pm
Viewing 15 posts - 1 through 15 (of 62 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy