Viewing 11 posts - 16 through 26 (of 26 total)
Oh - yes I did run it from the dB in question.
December 1, 2011 at 11:21 am
The dB in question.
If I run this in the dB in question the user shows up. I get the 3 result sets.
SELECT * FROM sys.sysusers;
EXEC sp_helpuser;
If I run it...
December 1, 2011 at 11:16 am
Because the account is showing up as \Domain\UserName that does not work
The number of orphaned users fixed by updating users was 0.
The number of orphaned users fixed by adding new...
December 1, 2011 at 11:04 am
Well I am trying to get the 1 user that has a domain account to show up so I can change the permissions on it. Yes we are using AD,...
December 1, 2011 at 10:13 am
I've tried that and double quotes, single.
I've tried stuff I knew wouldn't work.
December 1, 2011 at 10:10 am
In SQL 2008 R2 the EXEC sp_revokedbaccess 'domain\UserName' does not remove the user from the sysusers table.
I have tried sp_revokedbaccess,sp_dropuser, and sp_droplogin with and without [], '' and with the...
July 19, 2011 at 8:32 am
Yes. It actually looks like it is coming from NetApp. I guess tha if you have a virtual SQL server and running ComVault for backups (netApp in the background) this...
July 8, 2011 at 9:10 am
All great info.
I changed the encryption to none, but it made no change.
What I did find out is the SQL Agent was running under the Local System and it...
June 29, 2011 at 11:13 am
I read all of this thread and it does not pertain to my situation. Any help would be great!
I am getting the same error "The AcquireConnection method call to the...
June 29, 2011 at 9:23 am
I found that and tried it - no such luck. http://support.microsoft.com/kb/918992
master..sysxlogins does not exist - syslogins does of course, but the scripts as is does not work.
What I...
May 18, 2011 at 2:13 pm
Viewing 11 posts - 16 through 26 (of 26 total)