Tag Info

New answers tagged

1

I blogged about it exactly one month ago. Since link-only answers are discouraged and pasting here the whole blog post would be ridiculous, here is a summary of what you will find there. Basically, you have to record index usage in a user table, in order to make sure that server restarts and index maintenance don't delete entries for the databases you're ...


2

Got a suggestion on looking at index usage history, anyone happy to share a script please Below Script would get you the index usage history: From below, we can get an idea of how many seeks, scans, lookups and overall updates (insert, update and delete) occurred DECLARE @dbid INT --To get Datbase ID SET @dbid = Db_id( ) SELECT Db_name( ...


2

This is a common issue, you want to use groups to keep things simple but you don't want to lose visibility of who has access to your databases. The way I see it you have two options: If you trust your AD admins (If you don't you have bigger problems) then use AD groups. If you don't trust your AD admins then you will have to manage access on a per user ...


0

The query below will show you all of the users who have permissions on the server but do not have explicit permissions on the databases. SELECT P.name , D1.name AS DatabaseName_1 , D2.name AS DatabaseName_2 FROM sys.server_principals P LEFT OUTER JOIN <Database1>.sys.database_principals D1 ON D1.[SID] = P.[SID] LEFT OUTER ...


16

No. While the documentation currently has the following arguably ambiguous statement about what this flag means: Password policy is checked. What it really means, and should say, is that the flag serves two purposes: The password policy might have been checked, but only if (a) the password policy was enabled at the time the password was last ...



Top 50 recent answers are included