Uncategorized

Are You A SQL Server Architect, Designer, Engineer, or … ?

Continuous Protection
Have you ever wondered what happens to the information *between* backups of your database and the associated transaction logs? The short answer is that it depends. It depends on the solution you have in place – and one great approach is Double-Take – the software provides affordable recoverability, including continuous data replication and fail-over protection. Get more information here and see if it may be just the thing for your servers.

Featured Article(s)
Troubleshooting SQL Server 2005 Management Studio
In this article, Alexander Chigrik explains some problems you can have with SQL Server 2005 Management Studio.

Video Programs/Shows available:
[Watch] Disaster Recovery and Response Planning
[Watch] SelectViews – the Accidental DBA – tips, tricks and thoughts
[Watch] SQLonCall: Manager or Leader

Thoughts on Being A SQL Server Architect
Our frequent commentator, David, wrote in with some thoughts on the whole Database Architect discussion that I thought I’d share – "When I finished my undergraduate work, I was accepted into two graduate architecture programs. I didn’t follow that path, but have had a life-long interest in architecture.

The interesting thing in the current SSWUG discussion, is that an architect never architects anything. At least, when referring to the traditional architect who designs buildings. That kind of architect designs things.

At first, I was really bothered by the use of Architect for IT roles. It did seem like job title inflation. Sort of like giving a custodian the job of maintenance engineer or calling a garbage collector a sanitation engineer.

But using architect as part of an IT position title does not bother me so much any more. For a while, I tried to mentally replace the word architect with the word designer. It rarely works very well. The title with designer in it seems more closely focused on a particular project, while the term architect gives the job a more universal or area-spanning focus.

So, my addition to the discussion of the job title is this: When the word architect is used, the job has more responsibility and authority to set standards for the IT department or the enterprise."

Featured White Paper(s)
Making Databases Explorable
This paper looks at common difficulties encountered when maintaining a large number of databases and how the products in the … (read more)

The High Performance DBA: Optimizing Databases for High Performance
The combination of a cross-platform environment, added database complexity, more data, and less head count has become a real c… (read more)