Viewing 15 posts - 3,931 through 3,945 (of 6,679 total)
A couple of points on your process:
Item 1: SQL Server service accounts should not be setup as local administrators. Whether or not you use a domain user or local...
April 17, 2010 at 9:34 am
You use the procedure sp_change_users_login with the auto login parameter and identify the login/user to be fixed.
Look up the procedure in Books Online for exact syntax and available parameters.
April 15, 2010 at 8:03 pm
Yes, definitely update to the latest service pack. And also make sure your client tools are at least the same version (if not greater) than any instance you are...
April 15, 2010 at 8:02 pm
How did you copy the mdf/ldf files in the first place? Did you shut down SQL Server first - then copy the files? If so, then attaching those...
April 14, 2010 at 8:43 pm
Well, first of all you shouldn't be allowing your databases to autogrow. You should manually grow them out to at least 6 months of space and monitor the usage....
April 14, 2010 at 8:34 pm
In addition to what the others have stated, both Quest and SQL Backup utilize multiple 'threads' for the backup process - reducing the time it takes to backup in addition...
April 12, 2010 at 2:40 pm
If you want to create all logins from prod - then sp_help_revlogin would be the way to go. I didn't want all users on the prod system, so I...
April 10, 2010 at 9:00 am
First, you have to create the login on the secondary server with the same SID that exists on the primary server. Lookup CREATE LOGIN in BOL for exact syntax,...
April 9, 2010 at 10:04 pm
Yes, that's all you should need to do.
April 9, 2010 at 1:42 pm
Reorganize is fully logged, rebuild can be minimally logged when the recovery model is simple or bulk-logged. Either way, the transaction log backup after that operation will be very...
April 8, 2010 at 11:07 pm
george sibbald (4/8/2010)
whether...
April 8, 2010 at 10:07 pm
I did something similar using Powershell and SMO - you only need to install Powershell on your CMS server and use that instance to query all of the servers.
Or, you...
April 8, 2010 at 10:02 pm
Indianrock (4/8/2010)
April 8, 2010 at 7:38 pm
2Tall (4/8/2010)
That worked. However from the research I have done it appears I am unable to explicitly GRANT View to the users default database.Any thoughts,
Thanks,
Phil.
That is correct - deny supercedes...
April 8, 2010 at 5:59 pm
You have to put the AD group in brackets:
Deny View Server State To [DOMAIN\AD Group Name];
April 8, 2010 at 7:00 am
Viewing 15 posts - 3,931 through 3,945 (of 6,679 total)