Good Morning Everyone, Thank you for your patience while I dug up the answers to your questions regarding SQL 2005. I want to say thank you to everyone came to the event. Hopefully everyone attend the Tulsa Microsoft Windows User Group that evening, if you did not make it our to the event please check them and out and join.
You can learn more here: http://www.tmwug.org .
Here are the questions I took down at the event. Please comment if you have any further questions or if I missed any.
Q: Can you upgrade Small Business Server SQL 2000 to SQL 2005?
A: The feedback I have gotten is that technically you can upgrade to SQL 2005 but it is not supported!. However, with Windows Small Business Server 2003 R2 will add SQL Server 2005 Workgroup Edition for Premium Edition customers, there are also a lot more enhancements to this moving forward. For more information on SBS and SBS R2: http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/generalfaq.mspx
Q: How does SQL 2005 handle online databases during the upgrade, what about the applications that are in use?
A: This questions was very interesting to me so I did some checking. The best bet to see how this is going to work, is to use the Upgrade Advisor, this will give you great advice on any potential database or application issues. However ultimately for any upgrade, some good ole’ fashion testing is in order. For more information, and to down load the Upgrade Advisor look here: http://www.microsoft.com/downloads/details.aspx?FamilyID=cf28daf9-182e-4ac2-8e88-f2e936558bf2&DisplayLang=en
Q: Can I put Visual Source Safe components into SQL 2005?
A: Yes. If you have installed the Microsoft Visual SourceSafe 6.0 client components on your machine, SQL Server 2005 Management Studio will automatically detect that the VSS plug-in is available. As noted above, you can find the VSS plug-in listed in the Tools/Option dialog, by selecting the Source Control and then Plug-in Selection node. Also, the Source Control option in the File menu drop down becomes active, and from there you add an existing Management Studio solution to source control, or open a Management Studio directly from source control. You can enable multiple source control systems, and change from one to another. For more information on this check out this article: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/TSQLQueries.asp
Q: Is there Group Policies for the surface area configuration settings?
A: As of this writing, I could not find any Group Policy for this. However with the ability to get the settings to an .XML file, you can easily use the command line version of the tool (SAC.exe) to deploy these settings to other SQL servers.
Q: How do SQL Clients fail over when the mirror fails?
A: It really depends on the client application and how it was written. Client applications written using ADO.NET 2.0 will automatically fail over when the database fails over. However other clients will have to manually fail over. Mirroring has always generated some great questions. John Baker has a great post on mirroring.