One of the lesser used features of SQL Server 2000, but the capability to restore your databases to a particular point in time can be a valuable skill. Kathi Kellenberger takes a moment to explain how this feature works and how you can use it in your environment.
In the first article of this series, we presented the basic concepts relevant to understanding SQL Server 2005 Integration Services, which is the primary mechanism for Extraction, Transformation, and Loading (ETL) functionality available in SQL Server 2005. We also provided a quick overview of tools that allow you to manage such activities as DTS package design, development, and storage, as well as interactive and scheduled execution. In order to gain better familiarity with each of these activities, we will look at them from a more practical perspective, using a number of fairly straightforward examples.
One of the SQL Server 2005 Beta 2 features that has undergone considerable architectural, functional, and interface changes, compared with its earlier versions, deals with extraction, transformation, and loading (also known as simply ETL) of data. (In other words, allowing you to move data between a variety of stores and to modify it in the process, according to your arbitrary requirements). While in SQL Server 7.0 and 2000, such capabilities have been provided by Data Transformation Services (DTS in short), Microsoft decided that the degree of modifications introduced in the new version justified re-branding it, hence its rearchitectured and significantly improved implementation has been introduced under the new name of SQL Server Integration Services (SSIS).
This is the first article in a series on writing stored procedures using the Common Language Runtime (CLR). This article focuses on basic C# syntax and using Visual Studio to build a stored procedure. It's targeted at DBA's and anyone else who primarily writes in Transact-SQL and hasn't had much exposure to .NET yet.
TechEd is a great show and while the PASS summit is the best one for DBAs, this one is great for most of the other Microsoft technologies. Read about Day 3 from Steve Jones.
The SQL Server 2000 Query Optimizer is one of the more complicated things that a SQL Server DBA deals with. For most of us, we just let it work and do not give it a second thought. But when a crisis occurred, Andy and Steve had to dive in to learn a few more things about it.
Day 2 from TechEd, this time from Brian Knight's perspective as the SQLServerCentral.com crew enjoys a week of learning and sun at the 2005 conference.
We would like to offer a free copy of the May 2004 SQL Server Standard magazine to everyone who can take a couple minutes to update some demographics for us.
They have been very hard at work trying to get SQL Server 2005 ready for release, but many of them have been given a week's break after IDW15 to come down to TechEd. They've created an interesting diary that you can view.
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers