I had a DB stop working after a refresh and using these awesome scripts. the issue was the stupid vendor used the DBOWNER for permissions.

so I added this to the STORE proc near the top of the INSERTS

INSERT permission_store
select ‘exec sp_changedbowner [' + suser_sname(owner_sid) + ']‘as Command,
0 as run_order
from sys.databases where sys.databases.database_id = DB_ID()

then I restored a DB from prod to DEV and all the windows users were unable to connect to the db. some digging and I noticed that the “store” proc wasn’t saving “window_user”data.

I changed the following snippet to use:

INSERT permission_store
SELECT ‘IF NOT EXISTS(SELECT * FROM sys.database_principals WHERE name = ”’ + name + ”’) CREATE USER [' + name + '] FOR LOGIN [' + name + ']‘ + ISNULL(‘ WITH DEFAULT_SCHEMA=[' + default_schema_name + ']‘, ”) AS Command,
1 AS run_order
FROM sys.database_principals
WHERE type_desc in (‘WINDOWS_GROUP’, ‘SQL_USER’,'WINDOWS_USER’)
and type ‘S’ — don’t need dbo, guest, sys, INFO_SCHEMA

let me know what you think, please.

The plan here would be to monitor to see what is using the space and address it accordingly. If nothing can be done to keep TempDB from growing then more disk space will have to be added.

Here is a great write-up to help figure out what is going on: http://technet.microsoft.com/en-us/library/cc966545.aspx

In the case where the actual_free_rows_per_page is less than 1 you have to look at your original fill factor and the reasoning for it. If the table can only hold 1 row per page then be honest with the fill factor and just set it to 100. If the index you are looking at holds 100 rows per page and is inserted into randomly and is getting to less than 1 free row per page before the next index maintenanace then it is time to adjust the fill factor.

The idea is to use the least amount of fill factor possible to minimize page splits. What that means for a particular index really depends on the purpose and use of that index.

Thanks

It’s funny that I am not the only one that uses the same system for everything.

I really liked some of your closing wisdom about actually going through the motion of avoiding troubleshooting when making a change -

“A single person should make the change so that the plan can be followed step by step. If something is missing from the plan then it should be added to the plan in case these steps need to be followed again or reversed to roll back the change.”

Absolutely! Great post.