We’ll I’ve finely broken down and started using Twitter.
I decided to go all out.
I’ve got TweetDeck for my PCs, and TinyTwitter for my BlackBerry. I tried TwitterBerry but didn’t like it very much. TinyTwitter has much more functionally. I also signed up for BrightKite to track my location.
I would have to say, that one of the coolest new features of SQL Server 2008 is the ability to pass a table as a single parameter to a stored procedure.
While we have been able to do this in the past, by using XML to pass more than one value in, then break it apart. But this is just such a simpler, easier, more elegant solution.
SQL Server 2005 introduced us to Instant File Initialization. This allows SQL Server to create files of any size without sitting there for minutes or hours (depending on the size of the files).
While this is great when creating your database, or extending your database files there is a cost to doing so. Before each data page is written the SQL Server will write all zeros to the page. It also has the potential of a security issue as any data fragments which are in the space which the file took up are going to be included in the backup and could then be read if the backup was lost.
If you are like me you work with Exchange, and probably have to work with Exchange Server at least some times, and you may some all sorts of questions about it. Well here is your chance to ask some of the top Microsoft Exchange MVPs all those questions. Combined the MVPs on this chat have over 20 years as MVPs.
You can read more about the webcast over on ucblogs.net including the time and registration information.
For those of you who are SQL Server Magazine Subscribers you should be getting your copies right about now (if you haven’t already). When you do be sure to check out the article which I have in the magazine about clustering your SQL Server.
For those without a subscription you can sign up for a digital subscription at SQLMag.com and read the article on the web.
Gain access to SQL Server experts and learn more about SQLServerPedia.com by attending this webcast. SQLServerPedia.com is the free reference resource created for SQL Server professionals, by SQL Server professionals. See how you can access video training, as well as sample scripts for backup and recovery, index maintenance and performance tuning. Plus, boost your SQL Server rock star street cred in the SQL Server community by contributing articles yourself.
The Editor-In-Chief of SQL Server Pedia, myself and some (hopefully all) of the other editors of the SQLServerPedia.com Wiki will be on the webcast.
You can register for the webcast on the registration page.
See you on the webcast.
The SoCal Code Camp website has started accepting sessions for the next Code Camp in January. I’ve put a couple of sessions up there already.
I’ve got one on SQL Server Indexing for the Client Developer, and one on SQL Server Service Broker Advanced Performance Tips and Tricks.
I’m open to suggestions as to what the folks in the area who might be attending as to anything else SQL Server they night be interested in hearing about.
At the moment on Woody Pewitt and I are the only people who have sessions posted. I’m sure that will change shortly.
After you have created your tables, and stored procedures you will have a basic idea of what queries are going to be running against your database. If you haven’t already done so, its now time to start adding indexes to your database. The catch with index is that there is such a thing as to much or a good thing. As you add more and more indexes to your database your INSERT, UPDATE and DELETE commands will being to slow down, as each time you insert a record the insert is committed to the table, as well as to each index on the table. Continued »
All to often articles and presentations about storage work under the assumption that you have a typical OLTP database with mostly reads. However there are plenty of databases out there which are mostly writes and very few reads. Setting these systems up takes a different technique for best performance.
In my just released article on SearchSQLServer.com called “How to configure storage in SQL Server DB with more writes than reads” I go over some of the differences between a normal OLTP database and a high write OLTP database.
There are a few basic operations which SQL will perform when looking for the data that you need. Here they are listed in the order of worst to best.
- Table Scan
- Clustered Index Scan
- Index Scan
- Clustered Index Seek
- Index Seek
The basic rule to follow is Scans are bad, Seeks are good.