We all know what the ideal application design environment is for building a database back-end: an experienced DBA takes inputs from end users and developers and creates the database design in order to support the application being developed. But in reality, we don't get the opportunity to do application design like this very often. This article covers how to quickly find and fix problems in a design.
Ever need to recover a single package? Don't have local backups? Read this!!!
Want to learn more about some of your favorite authors. Check out this interview with Robin Dewson.
So, you've created a database and application and want to see how it operates with a substantial load of data In this product review of Datatect 1.6, you can learn how this third-party product could help you benchmark you database with a lot of sample data.
This article delves into the mysterious xmlHTTP object and the supporting ASP code. I've got to tell you that I really love using this object. Basically what I like about it is that through xmlHTTP you can expose some or all methods of any ActiveX class to the client-side user. What this means is you are giving the user the capability of calling your back-end Active X controls. And the best part of it all is that the entire communication process takes place behind the scenes!
Recently while working on the SQLServerCentral.com site, Leon Platt ran into an interesting ADO gotcha that he demonstrates in this quick tip.
From a DBA's point-of-view, the bigger the SQL Server box, the better. What would you consider to be the ultimate SQL Server box?
DBAs often ask how to transfer DTS packages and move them between servers. They also want a version control system that is more robust than that provided in msdb. Steve Jones looks at one of the features of the DTS designer that solves both of these problems.
By Steve Jones
vicarous – adj. curious to know what someone else would do if they were...
Say we have a database that we want to migrate a copy of into...
We are trying to get apps and users off of using SQL accounts to...
Hi I have this view to check if a job is running: SELECT...
All, if you are like me and do not care for the built-in color...
Certain internal SQL Server actions cause internal checkpoints. Which of these actions does not cause an internal checkpoint?
See possible answers