Viewing 15 posts - 256 through 270 (of 6,105 total)
dioscoredes (4/19/2011)
April 19, 2011 at 8:03 am
I prefer the use of SQLPing (especially command-line) or the Quest Discovery Wizard (which can also be used command-line as it licenses components of SQLPing). The reason it can take...
April 19, 2011 at 7:57 am
alen teplitsky (4/18/2011)
this is also a good way...
April 18, 2011 at 8:48 am
dioscoredes (4/18/2011)
April 18, 2011 at 8:46 am
jinlye (4/15/2011)
this seems like a lot of effort and increased overhead on your SQL database, for something that can be handled much more efficiently at the transport layer
If in your...
April 15, 2011 at 8:24 am
[Jim].[dba].[Murphy] (4/11/2011)
April 12, 2011 at 8:28 am
This is pretty easy, then. Create a new blank database. Identify what objects the public role has access to, specifically the stored procedures, since that's what you're targeting. Take Lowell's...
April 8, 2011 at 8:53 am
I'll give the general caution not to undo the permissions Microsoft defines in their initial install of these two versions. Otherwise, you could result in an unsupported configuration.
April 8, 2011 at 8:41 am
Whisper9999 (4/7/2011)
April 7, 2011 at 12:18 pm
Keep in mind that while you can remove BUILTIN\Administrators from the sysadmin role, this is just low hanging fruit. NT AUTHORITY\SYSTEM is still present with sysadmin rights (the VSS writer...
April 7, 2011 at 11:53 am
sehgalnamit (4/7/2011)
Is it possible to use my windows AD policy for my SQL server accounts like "sa"?
Yes. See here Books Online: Password Policy
And how can I get notification when my...
April 7, 2011 at 8:54 am
I understand.
SQL Server 2005 introduced the capability to take account policies from the local Windows machines. These are applied to SQL Server based logins like sa.
So the things we enforce...
April 7, 2011 at 7:30 am
You cannot modify SQL Server's set password ability without resorting to an unsupported system. Also realize that as of SQL Server 2005, if you use password policy enforcement, SQL Server...
April 7, 2011 at 2:31 am
It should not occur with an ALTER. If you see that, please report it via connect.microsoft.com as a bug.
With that said, starting with 2005, you can apply permissions at the...
April 7, 2011 at 1:45 am
You will need to grant the appropriate CREATE statements. In 2005 and above, you will also need to grant ALTER SCHEMA on those schema where these objects appear. The problem...
April 6, 2011 at 1:35 pm
Viewing 15 posts - 256 through 270 (of 6,105 total)