Database
Some of the new features of the 2005 version include tight integration with the .NET runtime (SQL Server acts as a host for the CLR), which enables you to write UDFs (user defined functions) and UDTs (user defined types) in C# or VB.NET code; the introduction of XML as a native data type (which means you can chose XML as the type for a column, and you can use special functions and operations to run very fast queries and filters on this column and its index); new functions (such as ROW_NUMBER, which makes it very easy to implement custom pagination; the Service Broker technology, which enables building message-based asynchronous database applications; much finer security permissions; and much more. The limitations of the Express version are that it supports only one CPU, only 1GB of RAM, and the maximum database size is 4GB. Advanced features such as database partitioning, database mirroring, notification services and full text search are also not supported. However, for most small to mid-size sites, SQL Server 2005 Express is an acceptable choice. You can start with it, and should you need more performance on high-end servers, you can upgrade to one of the other editions (Workgroup, Standard, or Enterprise) with no code changes required.
A final advantage of the Express edition that I want to highlight (and one that I'm sure will make many developers happy) is the new XCopy deployment: You can just put the .mdf database file on a local subfolder (there's a special /App_Data folder for web sites) and attach it dynamically by specifying the file path in the connection string by using a new attribute named AttachDBFilename. This makes it possible to XCopy the site's whole folder structure to the remote server, and you're ready to run without having to do any configuration work to the database server!
Database creëren
-- If database does not exist, create the database IF EXISTS (SELECT name FROM master.sys.databases WHERE name = N'Mikmak') BEGIN DROP DATABASE Mikmak END CREATE DATABASE Mikmak GO