The Database Weekly Update for June 30, 2008
Steve Jones looks back at a week of news on data center infrastructure, the EF war, and SQL Server 2008 news.
Steve Jones looks back at a week of news on data center infrastructure, the EF war, and SQL Server 2008 news.
Steve Jones looks back at a week of news on data center infrastructure, the EF war, and SQL Server 2008 news.
SQL Server high availability. Log shipping or replication, clustering or some other solution. It's a challenge and as companies grow more dependent on their databases, it's one that more and more DBAs face everyday. Paul Ibison has taken a look at how log shipping and replication can be compared in the quest for high availability.
SQL Servers seem to proliferate in many companies, making management a headache for DBAs. Steve Jones asks a Friday poll about how you handle all those service account.
See an example of using the Many-to-Many dimension in SQL Server 2005 Analysis Services to analyze sales data, and get ideas for other uses such as treating medical conditions, software testing, and more.
SQL Server expert Denny Cherry explains how SQL Server determines how much memory is used for procedure and buffer cache and how you can allocate available memory.
This article describes how to generate the sp_who2 results including the query text for the spid.
Training in the UK this fall from a variety of SQL Server experts. If you are in the area, I'd recommend one of these classes.
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...
Comments posted to this topic are about the item What Are You Waiting For?
Komplek Permata Kota, Jl. Pangeran Tubagus Angke No.170 Blok L Kav 8 & 9,...
BCA Finance Samarinda Telpon/WA:08218168291.Jl. Jend. Sudirman KCU BCA Sudirman No.30 Lantai 4, Ps. Pagi,...
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers