SQL Server 2000 had extensions built in to allow you to work with XML data, however, most installations did not work with it. XML has proven that it is a very powerful way of transmitting and working with data, but creating it from relational data has proven to be difficult. New author Hugh Lynch, CTO of Restricted Stock Systems, Inc. brin gs us a method for easily creating XML from your SQL Servers.
Right out of the box, SQL Server 2005 does not install many of its services (such as SQL Server Reporting Services) or does not have features turned on by default (.NET integration), thereby reducing the attack vectors that hackers could use to compromise your data security.
Check digits–not to be confused with checksums–are often added to numeric identifiers such as customer and product numbers to reduce the chance of incorrect entries. Sequences of numbers are notoriously easy to mistype, and constraints alone generally won't do the job. In this excellent article, Lynn Fields shows you how to implement the "Cadillac" of check digit methods–the Verhoeff Dihedral Group.
The fourth part of Steve Jones series looking at employee retention. In this article, he examines a few techniques that can help the employee ensure their own retention.
One of the most difficult database operations to scale-up on high-end server systems is the network call. In fact, without special precautions, a high call volume database application can have severe negative scaling on large systems. It is suspected that this problem is more pronounced on NUMA systems than basic SMP systems. A NUMA system with 16 processors can have significantly lower throughput capability than an otherwise comparable 4-way SMP system.
Auditing, analyzing and documenting your SQL Server installation is becoming more important all the time, especially as more and more attention is being paid to the security of your environment. Chad Miller brings us a look at a framework and a sample document you can use in your environment to conduct an audit.
There is an important technique for creating truly agile databases that I haven’t seen in his writings; one which is well-known to DBAs, but little understood in the application development community – the use of database views to create a layer of abstraction between the normalized relational tables and the applications that use the data.
SQL Server 2000 has a great job and alert subsystem, but it doesn't do everything. There are times when you want to be notified that something has completed, or not completed. New author Frank Loschiavo brings us a way to ensure that when you run a query you are notified if and when it completes.
In this article, I will introduce a significant improvement that underlies the new Analysis Services development approach, the Data Source View. A Data Source View is a design-time object that makes its home in the workbench environment of the Business Intelligence Development Studio.
In testing your applications, one of the things that you often want to do is run through a list of all possible values for some particular piece of code. Eli Leiba brings us a method for autmatically generating all the possible permutations for input values.
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
Comments posted to this topic are about the item Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers