SQL Feather and Quill

Here’s this week’s challenges:

- Installed and configured SQL 2005 Reporting Services on two Servers.
- I kept getting an error when installing SQL 2005 on a different server. The source was a network drive that had the install on it. It would get to VSS writer and then bomb every time. As it turns out, the folder structure on the share wasn’t the same names as SQL 2005 expects, so it would fail when it would look for the Tools folder.
- I created a script that appeared to fail for users on a new server. We had one chance to test it and it sort of worked. Everything looked correct in the security folders – except the AD groups in the database – they weren’t mapped to the correct group. To quickly fix it, I put a check mark by one group, and hit apply – they were automatically put in there proper role – interesting I thought. I hit apply and 10 minutes later the user was back saying she still couldn’t do what she was trying to do. Upon further review, I went back to the same screne and it was the way I found it originally. As we investigated, we found there was some groups that got change from Admin to Administrators and such. There were schema that were getting mapped to the Admin groups and it wouldn’t let us add any more groups. Further investigation will follow.
- Worked on documentation for cluster installs and read up on changing the SQL Service to “Affect the group” in Cluster Administrator.

Solution of the Week – sent in from Ola of http://ola.hallengren.com regarding my post on Tuning sys.dm_db_index_physical_stats. Ola writes, “I’ve developed a solution for index optimization that is using sys.dm_db_index_physical_stats. I haven’t