Hosting SMS in SQL Server
I am one of a group of DBAs who have done and continue to do Oracle work for several years. We having also been taking on SQL Server databases since last fall.
We have attempted to establish a standardized environment for each SQL Server instance and database to facilitate maintenance, backup and recovery.
Part of the standardization move now includes moving our SMS facility database into a standardized database. The group that manages SMS is quite nervous about this move and wants to maintain the kind of control they've had up to this point. I've also been told SMS "has a mind of its own" which I take to mean "may require configuration and privileges that are not common". In this organizational effort to bring administration of this database under a single DBA group I need to effectively support the needs of the SMS work group and as much as possible create a database environment similar to the 150+ we already have (in SQL Server). Here are my questions:
- If you have done something similar, are there any recommendations you would make?
- What is the most effective way for me to understand this tool (SMS) and its particular needs
- Other than inexperience with DBMS systems, what might make the SMS group nervous about this change?
I intend to address these same questions with the SMS group this week or next and intend to take a "try it and prove it" approach to address their concerns. If you have any insights or recommendations I would appreciate them.
Software/Hardware used:
Software/Hardware used:
ASKED:
May 12, 2004 10:48 AM
UPDATED:
May 12, 2004 11:23 AM
Answer Wiki:
Its really just important to understand the security SMS requires between its services and the SQL database. Microsoft suggests keeping the SQL database on the SMS server simply for performance reasons (i.e., SMS is in constant contact with the SQL database for updates, changes, monitoring, etc.). A lot of companies choose to move the database to another server, or install it on its own server during the initial installation, and it works fine.
SMS does fine-tune the SQL server services during installation to get optimum results, but being a dba you can probably find those performance modifications and duplicate them at the new location.
Probably the best resource for SMS, other than the MS site, is myITforum.com. Your primary issue is going to be keeping the required SMS security intact.
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
