A SQL Server 2005 feature that I appreciate and want to demonstrate is the OUTPUT clause. The OUTPUT clause helps in returning the actual data from a table soon after an insert. Applications require return values such as the new identity value, the computed column value or the default value generated by the default constraint.
2006-04-26
2,966 reads
This article examines the problem of complex data in integration projects and presents solutions for handling this data to create seamless integration throughout the enterprise.
2006-04-25
2,460 reads
Testing is key to ensuring a process actually works when it comes time to implement, rather than finding out when time may be of the essence. This holds true for testing SQL Server restores as well.
2006-04-24
2,625 reads
A SELECT query returns results as a rowset. You can optionally retrieve formal results of a SQL query as XML by specifying the FOR XML clause in the query.
2006-04-19
3,264 reads
Throughout our series of articles dedicated to SQL Server 2005 Integration Services, we have been working mainly with packages using the Business Intelligence Development Studio interface (although more recently, we also discussed SSIS-related functionality available in SQL Server Management Studio). Even though, as part of our exercises, we have worked with a number of packages, we have not yet explored the various options related to their storage. We will cover them in this article
2006-04-18
2,787 reads
In SQL Server 2005, you can explicitly or implicitly define the execution context. As we all know, a session starts when a user logs on to SQLServer or a connection to SQLserver is made. All operations in that session use the logon credentials used for connecting to SQL Server. When an EXECUTE AS statement is run, the execution context of the session is switched to the specified login or user name.
2006-04-17
2,799 reads
Have you started looking at what issues you might have migrating your existing applications to SQL Server 2005? If not then maybe as a first step, you should consider looking into what the SQL Server 2005 Upgrade Advisor can do for you. This article will discuss what the Upgrade Advisor is and how to use it.
2006-04-14
2,172 reads
You have many SQL Servers to administer and you just want to know when the last backup was taken for each database on each instance. This stored procedure will help.
2006-04-13
4,271 reads
Learn about SQL Server security techniques including the principle of least privilege, controlling metadata visibility, separation of users and schemas, and more.
2006-04-12
2,475 reads
Miguel De Icaza has been a major mover of Mono, the open-source framework for .NET since the get-go. These days he shepherds Mono along from within Novell Inc. At Novell's BrainShare conference, he discussed the latest doings with writer Paul Ferrill.
2006-04-07
1,567 reads
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
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...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
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...
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