If you're like Brian Knight, you probably have dozens if not hundreds of DTS packages running around that you're terrified to touch. SQL Server 2005 has some interesting methods to upgrade your packages to SSIS with minimal effort. This article shows you a few ways that you can use to upgrade and some of the drawbacks.
Database systems like Microsoft® SQL Server® have long supported triggers—developer-created scripts that automatically execute after or in place of INSERT, UPDATE, and DELETE statements. Because triggers can access the data modified by INSERT, UPDATE, or DELETE, they are an excellent tool for recording data changes to an audit log.
The SQL (Structured Query Language) language is a declarative language that became the "Data Language" used for describing "what I need" and "where to fetch it from" in most organizations. OOP (Object Oriented Programming) languages became the most common practice among developers widely adopted by R&D organizations around the world. So how do we bridge the gap?
A new feature for SQL Server? Steve Jones talks about a very interesting job posting from Microsoft.
Quickly becoming the SQL Server XML expert, Jacob Sebastion brings us a great new article that expands upon his very popular series on XML in SQL Server. This time he examines the FOR XML PATH option, which provides additional formatting capabilities.
People reading this post might really wonder of having read /heard about a concept on Dependency tracking in SQL Server 2008. It is nothing, but a set of built in existing SYS objects and their effective usage that help us save time & tedious efforts.
Every day, out in the various discussion boards devoted to Microsoft SQL Server, the same types of questions come up again and again: Why is this query running slow? Is my index getting used? Why isn't my index getting used? In order to arrive at the answer you have to ask the same return question in each case: have you looked at the execution plan? We are very pleased to be allowed to publish the first chapter of Grant Fritchey's excellent new book on execution plans.
SQL Server Integration Services is an incredibly rich and complex development environment that can handle almost any data movement task. Even those that do not involve SQL Server. Longtime author Tim Mitchell brings us a use that has nothing to do with SQL Server, but can be very handy for many of us.
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
By James Serra
I remember a meeting where a client’s CEO leaned in and asked me, “So,...
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
Hello team Can anyone share popular azure SQL DBA certification exam code? and your...
Comments posted to this topic are about the item Faster Data Engineering with Python...
Comments posted to this topic are about the item Which Result II
I have this code in SQL Server 2022:
CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
exec('SELECT ProductName FROM product;')
END;
GO
exec etl.GettheProduct
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned? See possible answers