The Checksum Transformation computes a hash value, the checksum, across one or more columns, returning the result in the Checksum output column. The transformation provides functionality similar to the T-SQL CHECKSUM function, but is encapsulated within SQL Server Integration Services, for use within the pipeline without code or a SQL Server connection.
DTS is a fantastic ETL tool and it is often used to import Excel documents. However this can be a manual process in many cases in setting up the package. New author Sloan Holliday brings us a way that you can leverage Office XP's automation facilities and XML to import data into SQL Server.
Usually developers like having full control over their reports but what happens if you have someone designated to build reports who does not quite know the backend schema. A good way to separate the building of the data for the report and the report design could be stored procedures. Now I consume stored procedures using Oracle which is not much different consuming stored procedures with SQL Server, however building the procedures is much different between the two. Even though I mention and show examples of stored procedures this is not an article for building them, just a guide for consuming a stored procedure within a Reporting Services Report.
SQL Server 2000 brought us DTS, a new way of working with data movement for SQL Server DBAs. However, unlike Integration Services and Project REAL, there weren't any great standards for working with this tool and building portable solutions was hard. Jonathan Stokes brings us a great article on how you can create a standard structure for your packages and make them more portable.
This is the forth article in the transaction and lock series. Up to now, the locks and hints discussed have applied to both SQL 2000 and SQL 20005. However, this article will introduce Snapshots, new in Microsoft SQL 2005.
Fragmentation in SQL Server is a huge debate. Does it matter? How much is too much? What should you do? In any case, new author Nicholas Cain has put together a system that allows him to keep track of the levels of fragmentation as well as defragment those tables when he feels they are getting too spread apart.
To null or not to null: that is the question. The specific focus here is performance implications of NULL versus NOT NULL columns.
I'm sure most DBAs don't give a second thought to starting and stopping their SQL Server 2000 servers. But do you know the different ways to do this and some of the impacts and expectations you should have? Especially with hardware growing, it's not always as simple and straightforward as it should be. Andy Warren recently had to deal with some issues and starts a new series looking at the various ways of starting and stopping SQL Server.
Part I of this article illustrated how to monitor CPU usage of running processes on a local machine or from a remote machine. This article illustrates how to monitor the CPU usage of different running processes on different machines and collect the information in a database.
SQL Server 2000 databases seem to move more often than their DBAs would like. However, moving the logins and users can prove to be a bit more of a challenge than just moving the databases. New author Corey Bunch brings us his technique for making this easier.
By Steve Jones
dorgone– adj. wondering if you could slip away from an event or group conversation...
By ReviewMyDB
Many of us use AI the same way every single day. Open a tab....
By SQLPals
SQL Server Transaction Log Forensics: Preserving Evidence During an Incident SQL...
Could you please let me know if anyone is used https://github.com/ktaranov/sqlserver-kit github for deployment...
I’ve been looking into ways to improve the connection between a website and its...
Comments posted to this topic are about the item When And How to Automate?
How many Azure SQL DB Hyperscale HA replicas can be configured as of Sept 2026?
See possible answers