mei 2007 - Posts
I once posted some information about the 3GB, AWE and PAE settings.
Here is some more detailed information about these settings. Definitely worth reading!
I recently stumbled upon a KB article (KB917828) that points out some situations in which your procedure cache is cleared.
Since one of our architectures for reporting involved database snapshots I was suprised to read that your whole procedure cache is cleared when you drop a database snapshot. This may not be as dramatic as it sounds but you should closely watch the impact on your environment when the cache is cleared.
Other situations are:
- A database has the AUTO_CLOSE database option set to ON. When no user connection references or uses the database, the background task tries to close and shut down the database automatically.
- A database has the AUTO_CLOSE database option set to ON. Maintenance operations are performed, such as the DBCC CHECKDB operation or a backup operation. When the operations finish, the background task tries to close and shut down the database automatically.
- You run several queries against a database that has default options. Then, the database is dropped.
- You change the database state to OFFLINE or ONLINE.
- You successfully rebuild the transaction log for a database.
- You restore a database backup.
It is announced to be available in 2008.
I'm ready for a beta/ctp version ;-)
More information here and here.
Datasheet here.
For those of you who are lucky and are already working with VSDBPRO, there is a service release CTP available for download (KB936202).
Make sure you read the release notes before you install.
Gert Drapers also posted some additional information on his blog.
One of the biggest enhancements, in my opinion, is the support for SQLCMD variables. This enables great flexibility in your deployment scripts.
We were troubleshooting a long running batch job when we suddenly realized that there is no easy way to get wait information for a specific session or query. With the rich information already available to us in SQL Server 2005 this might be a great addition to the product.
I decided to launch a suggestion on Microsoft Connect. This great
initiative makes it possible for everyone to give suggestions to improve Microsoft's products.
Check out my suggestion here (and while you are there do vote 
)