Viewing 15 posts - 3,376 through 3,390 (of 7,168 total)
rhythmk (8/16/2012)
JAZZ Master (8/16/2012)
Cliff Jones (8/16/2012)
Daniel Bowlin (8/16/2012)
Cliff Jones (8/16/2012)
Ray K (8/16/2012)
rhythmk (8/15/2012)
Daniel Bowlin (8/15/2012)
contentSatisfied
Satiated
Saturated
Color
Scheme
Plot
Story
Epic
August 16, 2012 at 9:20 pm
Perry Whittle (8/16/2012)
Correct you can't drop the user, you change the mapping.
You cannot change the login mapped to the dbo user either...at least I could not on 2005, 2008 R2...
August 16, 2012 at 9:19 pm
I did not have any luck using ADSI:// myself. Only when switching to use LDAP:// did it work although it sounds like you had a few things going on simultaneously....
August 16, 2012 at 9:13 pm
surma.sql (8/15/2012)
i have question about SQL Server Jobs
I check the job properties and see the username is 'SA'. and i check into steps and there is no user is specify...
August 16, 2012 at 3:52 pm
Suresh B. (8/15/2012)
1) If you run a job manually, it runs using your login.
2) If schedule it, job runs using SQL Server Agent service...
August 16, 2012 at 3:46 pm
Catch it from where? In T-SQL or an app language like C#?
If your supplying a severity level of 10 then it will not trip a T-SQL CATCH block. Your RAISERROR...
August 16, 2012 at 3:14 pm
No need to script them out. You can generate a command like this for each user with the new login for each. Just make sure you supply the NAME option...
August 16, 2012 at 2:24 pm
Does this occur when you first start the server or intermittently after running for a while? The problem is likely related to the storage subsystem temporarily being viewed as offline...
August 16, 2012 at 1:40 pm
August 16, 2012 at 1:15 pm
Try it with LDAP instead of ADSI:
Select [Name] ,[DisplayName]
From OpenQuery
( ADSI,'SELECT name, displayname FROM ''LDAP://RHSPWDCOC02''
WHERE objectCategory = ''Person'' AND objectClass = ''user''')
August 16, 2012 at 1:10 pm
I won't say incorrect because your situation may truly be unique, but personally I think you're approaching this from a very difficult angle, i.e. trying to contort the database server...
August 16, 2012 at 9:55 am
Pablo Campanini-336244 (8/16/2012)
You are absolutely right, I am using SQL Server 2008, not SQL Server 2008 R2, and the bug is killing me!!!!!!.
I will ask my boss to upgrade to...
August 16, 2012 at 9:40 am
Happy you got it sorted. I was curious so I did some looking to see if others had this issue and it looks like it may be a known bug...
August 16, 2012 at 9:14 am
Viewing 15 posts - 3,376 through 3,390 (of 7,168 total)