Monday, March 31, 2008
Sunday, March 30, 2008
Supported .NET Framework Libraries
This means that in order to use components of the .NET Framework that are not supported, you have to first create them as a, generally UNSAFE, Assembly in the database. This however can lead to support issues with Microsoft Support, according to their KB Article
Bob Beauchemin covered this in a recent blog after upgrading .NET on a SQL 2005 Server. If you choose to reference an unsupported Assembly in your CLR code, your Assembly will cease to function and execution will result in an exception with Message 622 and an error ending with:
Assembly in host store has a different signature than assembly in GAC.
To correct, you must drop your assembly as well as the unsupported assemblies, and add them back so the GAC is refreshed with the newer version.
Wednesday, March 26, 2008
Wednesday, March 19, 2008
Kevin and Hilary also held a 2 hr questions and answers session on the coming release of SQL 2008. Of particular interest to me was the lack of knowledge surrounding Powershell integration in the room. Also lacking heavily was knowledge about the new policy Management in SQL 2008. Both of these are newer features, and only those testing the CTP's or following them closely would be aware.
I have been playing with the DMF/Policy management since installing my Feb CTP and plan to post more information on this in the days/weeks to come. From there I guess I am going to move on to Powershell and play around with it.
Thursday, March 6, 2008
While working on testing the upgrade path from SQL 2005 to SQL 2008, I came across the following mesage when using the Upgrade Analyzer:
Message: SELECT failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or query notifications and/or xml data type methods.
This is very odd to me because the databases being upgrade have none of the above items in it. I did some searching online, and others seem to say that these messages are slightly vague. I did find a post on the MSDN Forums:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=659712&SiteID=1
but in the end I figured out that by resetting the ARITHABORT to on for all my databases would allow the Upgrade Advisor to pass this test.
sp_msforeachdb 'ALTER DATABASE [?] SET ARITHABORT ON WITH NO_WAIT'
Another thing I found with the Upgrade Advisor is it doesn't catch if you are not on SP2 or not, which is required in SQL 2005 to upgrade in place to SQL 2008. Once I fixed these two little items, everything else in the upgrade went smooth.
This post has been migrated to my new blog on SQLBlog.com. You can find this post at the following address:
Wednesday, March 5, 2008
It provides a stored procedure that can be run to update your indexing and statistics while maintaining support from Microsoft, and not breaking your search services. For further information about previous problems see:
Information about the Maintenance Plan Wizard in SQL Server 2005 and about tasks that administrators can perform against SharePoint Databases
Tuesday, March 4, 2008