Viewing 15 posts - 661 through 675 (of 2,436 total)
If you establish linked servers you can loop through sysservers and then use a 4 part query to get all of the information in just one QA session.
June 28, 2007 at 1:30 pm
I dunno ... If it were my server I'd be performing a master/msdb recovery ...
June 22, 2007 at 11:15 am
Lots of good stuff here. Basically I agree that SOX is a pain and those who know the least make the most mess procedurally for us DBAs. But now I...
June 22, 2007 at 10:45 am
Today is your lucky day ... I just ran into this information in another forum earlier this week ... try this:
use msdb
exec master..sp_addlogin 'testme', 'testme', 'msdb'
exec msdb..sp_adduser 'testme', 'testme', 'TargetServersRole'
grant...
June 21, 2007 at 8:14 am
Thanks Carl !
... yet another reason not to autogrow by 10% ...
June 20, 2007 at 9:08 am
Could you post the bat/cmd file ?
June 20, 2007 at 8:54 am
Here is a kinder and gentler way taken from a fairly recent post:
Try setting 'Auto Close' and then just check your SQL Server errorlog !
June 20, 2007 at 8:19 am
A database does not need to be in single user mode to modify size, growth or it's growth limiting factor. As for an SP, well you would have to write...
June 19, 2007 at 11:42 am
from BOL:
RESTORE DATABASE { database_name | @database_name_var }
[ FROM < backup_device > [ ,...n ] ]
[ WITH
[ RESTRICTED_USER ]
[ [ , ] FILE = { file_number...
June 19, 2007 at 10:55 am
It sounds as though you have non-DBAs using either the sa account or they have sysadmin server role. If either is true then the 'gremlins' may strike at you again ......
June 18, 2007 at 12:11 pm
Another question ... are you performing the backup to a local drive or a mapped drive ?
June 15, 2007 at 9:41 am
Viewing 15 posts - 661 through 675 (of 2,436 total)