Viewing 15 posts - 646 through 660 (of 6,105 total)
It's using the proper T-SQL command for SQL Server 2005 and above. You can see it here:
-- Login: BUILTIN\Administrators
IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE [name] = 'BUILTIN\Administrators')
...
February 22, 2009 at 3:50 pm
Absolutely. And remember in the case of Windows users to consider what groups they are members of that are granted access to SQL Server. SQL Server security works like Windows...
February 22, 2009 at 3:31 pm
Did you grant VIEW DEFINITION on a particular database per chance? If you granted VIEW ANY DEFINITION, as long as they have the ability to access the database, they should...
February 22, 2009 at 3:27 pm
The only gotcha with logon triggers is if there is an issue with one, it will prevent all logons except through the DAC.
Another option would be to build a...
February 22, 2009 at 2:43 pm
Is there an issue with you creating a local account on your laptop and using that for your SQL Agent processes?
February 22, 2009 at 2:36 pm
If you're dealing with SQL Server 2000 and below, here's the query that will reveal the Windows logins you have:
SELECT name FROM syslogins WHERE isntname = 1;
For SQL Server 2005...
February 22, 2009 at 2:17 pm
Since you're using SQL Server 2005, the catalog views you'll want to use are sys.server_principals and sys.database_principals (in each database). If you were using SQL Server 2000 or prior, you'd...
February 22, 2009 at 11:52 am
All logins are a member of the public role. Therefore, being a member of that role doesn't give you any special rights.
To have rights to control server properties, all properties,...
February 22, 2009 at 10:51 am
SQL Server MVP Jonathan Kehayias has posted a workaround he has found. It'll still mean you have to run an upgrade, but you won't have uninstall/reinstall.
February 20, 2009 at 10:32 am
No. You cannot remove from master and tempdb for sure. While it is possible in SQL Server 2000 for msdb, it shouldn't be done there. It's not supported in later...
February 19, 2009 at 2:32 pm
Chris Rowley (2/19/2009)
Just so that we're clear, are you saying that I don't even have to load a Cert for the traffic to be encrypted and the...
February 19, 2009 at 9:58 am
There isn't anything you need to do. Starting with SQL Server 2005, SQL Server uses TLS to encrypt the logon packets. It'll use its own self-signed cert if necessary. So...
February 19, 2009 at 8:16 am
There's been no official announcement beyond the BI upgrades, so far as I am aware. However, the updates such as Policy Management are certainly worth the upgrade now.
February 17, 2009 at 7:51 am
No. While the login name was case-insensitive if your SQL Server has a case-insensitive collation, the password is always case sensitive. This is because of the hashing algorithm used.
February 15, 2009 at 3:58 pm
Viewing 15 posts - 646 through 660 (of 6,105 total)