The Writing on the Wall
There is a world of difference between the business processes that really take place in a company and the management's understanding of those processes…
2006-04-27
2,351 reads
Additional Articles
OUTPUT clause in SQL Server 2005
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
Making Complex Data Simple: Transforming Your Data Transformation
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 SQL Server restores
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
Constructing XML Using FOR XML
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
SQL Server 2005 - SQL Server Integration Services - Package Management
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
SQL Server 2005's EXECUTE AS statement
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
SQL Server 2005 Upgrade Advisor
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
Stored procedure: Determine last database backup
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
Keep Bad Guys at Bay with the Advanced Security Features in SQL Server
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
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers