SQL Server 2008 Compression
Testing and analysis of new backup compression and table/index compression features of SQL Server 2008.
Testing and analysis of new backup compression and table/index compression features of SQL Server 2008.
Today Steve Jones talks about the challenges of deciding what to include in that next software release. Something that likely isn't as easy as we might think it should be.
We can all recognize good-quality database code: It doesn't break with every change in the server's configuration, or on upgrade. It isn't affected by concurrent usage, or high workload. In an extract from his forthcoming book, Alex explains just how to go about producing resilient TSQL code that works, and carries on working.
If you want to speak at this June 26 event, submit a session now.
Free webinar training brought to you by Pragmatic Works, WROX, SQL Server Central, and SQL Server Magazine. The April Series will run from April 20 - April 29, 2010. Register now to reserve a place.
Speed is critical. That's the theme for today's editorial, using the NYSE as an example.
SQL Server 2008 Full-Text Search feature can be used by application developers to execute full-text search queries against character based data residing in a SQL Server table
A funny example of SQL Injection has Steve Jones reminding us that every application needs to protect itself.
A new article from Wayne Sheffield that examines the ranking functions in SQL Server. Learn how you can use ROW_NUMBER(), NTILE(), RANK(), and DENSE_RANK() in your applications.
By Brian Kelley
My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...
By Steve Jones
“On the way to a grand goal, celebrate the smallest victories as if each...
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
Jl. Pemuda No.90-92, Kembangsari, Kec. Semarang Tengah, Kota Semarang, Jawa Tengah 50133
Menara BCA, Grand Indonesia, Jl. M.H. Thamrin No.1, Menteng, Kec. Menteng, Kota Jakarta Pusat,...
Jl. Jend. Sudirman No.233, Cubluk, Giritirto, Kec. Wonogiri, Kabupaten Wonogiri, Jawa Tengah 57611
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers