Viewing 15 posts - 166 through 180 (of 758 total)
The witness is used for automatic failover in High Safety mode - The database is not mirrored to the witness server
June 13, 2013 at 6:10 am
Shrinking MSDB will not affect your Log Shipping setup. You're not deleting any data from MSDB
June 13, 2013 at 6:07 am
June 13, 2013 at 6:02 am
I've dealt with corrupter maser databases before - Instead of rebuilding all system databses, which is the fix for master db corruption, I did the following:
Took a previous backup of...
June 13, 2013 at 2:59 am
I wouldn't worry too much about the DB logins and their permissions as these are stored in the user database itself.
The main thing is the instance level logins and...
June 13, 2013 at 1:32 am
Since you can't mirror system databases which is where this info is stored - The best thing to do is to script out the logins and permissions. Do this on...
June 12, 2013 at 4:23 am
System databases can be restored as user databases on your DR servers - Just keep track of which ones belong to which servers.
When you have downtime on the Prd servers,...
June 12, 2013 at 4:19 am
muthyala_51 (6/6/2013)
June 7, 2013 at 1:59 am
Make sure that the SQL Agent service account also has permissions to the share..
June 7, 2013 at 12:45 am
ikonrao (6/6/2013)
Or if we can get create table statement for that table,...
June 6, 2013 at 7:03 am
I would implement a "Log Shipping" scenario between the servers and then just cut-over when the time comes
June 6, 2013 at 2:00 am
Bpool (6/5/2013)
hi there,do we need to take SQL Services offline while applying service packs.
You don't need to take SQL Services down - Let the service pack do that for you,...
June 6, 2013 at 1:57 am
Raymond van Laake (6/5/2013)
I have a SQL 2008 R2, running on Windows Server 2008, with all latest service packs and updates. It runs approx. 30 databases that totals over 500GB...
June 5, 2013 at 5:30 am
Thanks
Will add it into my where wait_type not in() list
June 5, 2013 at 5:19 am
Viewing 15 posts - 166 through 180 (of 758 total)