The next TSQL Tuesday is only 1 week away. This month the topic covers getting a little R&R. We would like to know some of the things that you do in order to get the […]
T-SQL Tuesday #009: Beach Time Congratulations! You have been chosen as a finalist in the Vacation Getaway package of a lifetime. You will be flown to a resort destination of your choosing. For this vacation, […]
Observe and Report This month we get to frolic in our memories of school days. Thanks to HeadMaster Robert Davis (Blog | @SQLSoldier), we are entreated to a little detention while we figure out how […]
I see database compression, as offered with SQL 2008, to be more like these file compression utilities than DriveSpace. Data compression in SQL 2008 is not an all or none implementation. You get to pick and choose what gets compressed. That is a big time bonus for me.
In the DMVs for SQL 2005 and SQL 2008 there is more than one place you can find the information about the size of your LOB data? And it goes without saying that there is more than one way to find information about LOBs in your database.
Checking for BLOBs that were created in the Primary Filegroup by default. To move them was a manual process and is a different topic from the crux of this one. Since the initial report to find the BLOBs, I have evolved it somewhat to try and find the size of each object, as well as to report on the usage related with each.
When it is necessary to provide reports on activity occurring on the server, it pays to do a little prep work. Be Prepared. It is not an easy task to be able to go back in time and report on data that isn’t captured. The little prep work that one may need to do is well worth the effort in the end.
What if we could create a numbers table without IO? What if we could perform several different kinds of queries without IO? Itzik Ben Gan proposed a cascading CTE solution that does this sort of thing. This article shows that method in use to help improve certain IO conditions.
The puzzling problem I encountered in the article was a fun little job that kept giving different results than running the same code from SSMS. Check it out!