Blog ala Vidar

For those of you who thinks Katmai is a moutain, well.. I am not sure.

But, I do know that it’s the code name for the future version of SQL Server from Microsoft. They call it: Microsoft SQL Server 2008, “Katmai” June CTP

After reading the release notes from MS, I was very disapointed, but after testing it I got new hope. The first thing I layed my eyes on was something called “Declarative Management Framework” (DMF). This includes something I think we might use in the future: policies. I see great potential with these policies because you can setup naming conventions on the server. For example, you can deny saving tables with names that does not start with [as][tbl], or you can force login-names to start with a prefix (s for statoil, k for kellogg). With policies you can also set how much CPU a user can use.

To enable these options, I had to run:

C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BIN\sn.exe -Vr Microsoft.SqlServer.DmfSqlClrWrapper,89845DCD8080CC91

and then:

ALTER DATABASE [databasename] SET TRUSTWORTHY ON

Intellisence

I have tried this feature from Red Gate’s ”SQL Prompt”. To be honest, I am not a fan of this, because it is slow, it always gets in my way and I like writing the code myself. (used to vim and notepad ). BUT, I do understand that this is a very neat feature for others. Microsoft sais the only reason it didn’t come with this CTP is that they need to make it run faster.

Storing files

It should now be possible to use a mix of storing files to a fileshare and a blob-field. I have not found the details about this, but it is something about making an own filegroup (called FILESTREAM) and in this way combining fileshare and blob-fields.

Compability

For me, it seems like this should rather be called SQL Server 2005 SP1, than SQL Server 2008. In my opinion, there is not enough changes to make a new version. Anyhow. Omega already supports 2005, and I have tested an restore of R2CurrentBuild and we are compatible with the upcoming 2008 too!

PS! SQL Server 2008 compared to 2005, seems much like .NET 3.0 (3.5) compared to .NET 2.0.