Viewing 15 posts - 2,266 through 2,280 (of 6,105 total)
They do have such classes:
Updating Your Database Administration Skills to Microsoft SQL Server™ 2005
Updating Your Database Development Skills to Microsoft SQL Server™...
January 27, 2006 at 6:54 am
Yes, anyone who is a member of the local Administrators or Power Users groups have the ability to start and stop services.
January 26, 2006 at 3:18 pm
Well, I've written them before and actually, I just looked at subject for an article I completed in the last week. If it sees print, it'll be in SQL Server...
January 26, 2006 at 12:49 pm
This is a good article. I was working up an example query based on your exact table, just haven't had time due to too many things going on at work.
January 26, 2006 at 11:23 am
Okay... but whoever is conducting the audit hopefully realizes that this doesn't keep the user out of master. The guest user is enabled in master (and is required) and therefore...
January 26, 2006 at 10:21 am
Build a query like the following:
SELECT 'EXEC sp_defaultdb ''' + name + ''', ''<new database>''' FROM syslogins
And the output should be what you want. Out of curiosity, though, why are you...
January 26, 2006 at 10:06 am
No. Ownership chaining still exists in SQL Server 2005. There are features for impersonation on stored procedures and the like, but SQL Server 2005 still does a security check if...
January 26, 2006 at 10:03 am
Off the cuff, and by no means a complete answer...
1) How many installations of SQL Server are present (including ones on workstations) and what versions/service packs/hotfix levels they are at....
January 26, 2006 at 10:01 am
You have an ownership chaining problem. If the objects are owned by the same user, say both the view and the table, you only need to give permissions on the...
January 26, 2006 at 9:55 am
Think of those with sysadmin rights being like a security custodian in the military. Technically the security custodian can get to anything. There's a level of trust that he/she doesn't....
January 26, 2006 at 9:05 am
In the database itself:
EXEC sp_helprolemember 'db_owner'
And since sysadmin fixed server role members also have map in as dbo:
EXEC sp_helpsrvrolemember sysadmin
January 26, 2006 at 9:01 am
Yup, this one involves dynamic SQL. The key here is that the end user will have to have SELECT rights against the table where the pivot data is coming from....
January 26, 2006 at 8:59 am
If you can do a packet trace, that's the easiest way. Otherwise you'd need a tool like SQLCrack or SQL Squirrel (from NGS Software) on the old server. If you...
January 26, 2006 at 8:38 am
True, but if all are sysadmins, there's nothing stopping them from running the superuser procedure.
January 26, 2006 at 8:02 am
The same as it would in any other situation. Robert Marda has several articles on the use of Dynamic SQL and the problems therein. SQL Server 2005, at least with...
January 26, 2006 at 7:51 am
Viewing 15 posts - 2,266 through 2,280 (of 6,105 total)