Featured Article(s)
Design and implement Database partitioning using GUI in SQL server 2005
Design and implement Database partitioning using GUI in SQL server 2005
Can You Help Settle an Argument, er, Discussion?
I was talking with a DBA friend about what types of things are most common for a DBA to do in terms of maintenance and management.
Backups?
Recovery/Recoverability?
etc…
But the discussion came about when we were talking about performance management and tuning. My question was whether this was a hyper-critical aspect of DBA-ship at this point, or if hardware had gotten to the point cost-wise where performance was frequently solved by throwing hardware at the issue. I could argue this one both ways, and have seen it both ways at different locations and installations. Some tune, tune, tune their SQL Server to get the absolute best performance without touching hardware. Others have a policy of hardware first (more CPUs, more memory, etc.), then tuning the system.
And yes, you can take the easy way out and say "both" – but really – how do you approach this?
Do you have policies or goals for performance management and, if so, how do you make the decision to tune with hardware or diving into the tactical aspects of SQL Server processing?
New! SQL Server Video Program
(133) SelectViews: Proof: Chris Shaw talks to himself(!) plus interview with Paul Nielsen, Brent Ozar and Encryption. Information about the upcoming vWorkshop, tips, experiences and more.
[Watch the Show]
Previously:
[Watch] Snapshots as Backups? David Penton, Keeping Customers, Database Inventory and More
[Watch] Christopher Regan, Donald Belcham, John Welch
[Watch] Herve Roggero, Jason Strate, and TJ Belt
Featured White Paper(s)
Real-Time Data Integration for the SQL Server Data Warehouse
The Microsoft SQL Server database is becoming an increasingly popular platform for hosting data warehouse and operational rep… (read more)
H B D C!