Viewing 15 posts - 1,606 through 1,620 (of 6,105 total)
sqldba (10/10/2007)
public role is something that i cannot REVOKE for UPDATE,INSERT,DELETE etc................ I am not sure that this PUBLIC role as to do with this issue.
Everyone is a member of...
October 11, 2007 at 6:39 am
This is mostly easily done on the network side with an Access Control List (ACL) on the switch. However, on the server itself you could put an IPSEC Policy restricting...
October 11, 2007 at 6:36 am
Are you using a Windows login to connect to the first SQL Server? How do you have the linked/remote server security set up? Also, when you say data extraction tools,...
October 10, 2007 at 8:00 pm
fhanlon (10/9/2007)
October 10, 2007 at 6:37 pm
Pam Brisjar (10/10/2007)
Also, have you run upgrade advisor against the DB?
Make that 2 votes for the use of upgrade advisor. It'll do syntactical checking you'd otherwise have to do by...
October 10, 2007 at 6:13 pm
Greg Charles (10/10/2007)
October 10, 2007 at 6:10 pm
Louis' blog has a SQL script which will give you all the explicit permissions. From there you're going to need to check role membership. Also, if you're dealing with a...
October 10, 2007 at 1:27 pm
You'll need to query sys.database_permissions to get the full list of permissions. The system stored procedure sp_helprotect will not return information on securables that weren't present in SQL Server 2000....
October 10, 2007 at 12:33 pm
Another possibility is network I/O on the client side. If the client is buried under network I/O, you could see a difference. It depends on how big a difference there...
October 10, 2007 at 11:46 am
Remote Desktop: If they are making undocumented changes, yes, their access should be revoked. However, before doing so, you might want to audit that server to see what else changed.
SA...
October 10, 2007 at 11:34 am
vrkc (10/10/2007)
October 10, 2007 at 11:29 am
Theo Jacobs (10/10/2007)
October 10, 2007 at 8:40 am
There sounds like there is a security issue with the SQL Server you are trying to protect.
In order to connect, the client must have a valid login. How is the...
October 10, 2007 at 8:31 am
And be sure to do the normal security audits, especially to check when SQL Server is stopped and started. When SQL Server is stopped, the database files are closed and...
October 10, 2007 at 8:23 am
It should be noted that if you're using a named instance, you'll have to modify MSSQLSERVER and SQLSERVERAGENT to the correct service names. Also, the sc command can be used,...
October 10, 2007 at 8:19 am
Viewing 15 posts - 1,606 through 1,620 (of 6,105 total)