Viewing 15 posts - 3,511 through 3,525 (of 6,105 total)
In this case, if you can afford it, you may want to bring in consulting help to check things out. There should be someone locally in Des Moines who has...
April 30, 2004 at 7:29 am
Well, you'll likely need to write a few T-SQL queries to change the entries. You could find a names database (like a book of baby names or the like) and...
April 30, 2004 at 7:08 am
While it is possible you've been hacked, the database changes could have been done by anyone with rights, and that might have been an accident. The error being returned to...
April 30, 2004 at 7:03 am
A good starting point is the sp_who and sp_who2 system stored procedures (though sp_who2 isn't officially documented). These take information from a variety of system tables to include sysprocesses and...
April 24, 2004 at 3:06 am
You need to create what is called a MAPI profile for SQL Server to use for SQL Server Agent. Unfortunately, Outlook Express does not create a MAPI profile. Full blown...
April 24, 2004 at 3:00 am
SQL Slammer is a nasty worm, indeed. You'll find that while the OS gets patched fairly regularly, SQL Server doesn't have a whole lot of patches in comparison. BTW, Oracle...
April 24, 2004 at 2:54 am
I'm not sure that there's an easy way in Enterprise Manager if at all. However, in T-SQL using Query Analyzer you can do this using the system stored procedure sp_change_users_login.
April 24, 2004 at 2:49 am
The CDs with SQL Server, what is written on the face of the CDs?
April 24, 2004 at 2:45 am
The excerpt you submitted didn't give what process was running when the setup error came up, but here is a link from the Microsoft Knowledge Base. Perhaps that might be...
April 23, 2004 at 1:41 pm
What do the last few lines of the sqlsp.log file say? This is found in the %WINDIR% directory (C:\WINNT or C:\WINDOWS in most configurations). Does it indicate an error?
April 23, 2004 at 12:12 pm
The xp_cmdshell extended stored procedure is in the master database (as are all extended stored procedures). If you want to give access to xp_cmdshell without giving out sysadmin role rights,...
April 23, 2004 at 12:06 pm
Disregard that. Too early in the morning.
The error message is exactly right. You can't remove anyone from the public role. All users are members of the public role if they...
April 23, 2004 at 11:47 am
A couple of questions: Has anyone looked at the network traffic? Is the SQL Server an internal server or does it face the Internet?
April 23, 2004 at 6:59 am
In Query Analyzer you can use the system stored procedure sp_droprolemember. For instance:
EXEC sp_droprolemember 'public', 'UserToRemove'
April 23, 2004 at 6:57 am
Viewing 15 posts - 3,511 through 3,525 (of 6,105 total)