SQL Server Integration Services, the ETL subsystem for SQL Server 2005, is a new paradigm of development for the SQL Server DBA. It is one of the most popular, and also complex, environments that many people work with in SQL Server 2005. Amit Lohia brings us an introduction to this environment along with the basics of building and deploying a package.
2008-05-14 (first published: 2007-06-18)
25,666 reads
After quite a few versions, Enterprise Manager is being retired. SQL Server 2005 will have a new management tool called the SQL Server Management Studio (SSMS). Amit Lohia brings us a first look at some of the features of this new tool.
2006-11-24 (first published: 2005-07-07)
31,673 reads
One of the most popular questions on SQL Server 2000 deals with determining how much space the various tables in your database take up. There are a variety of reasons for this and a few ways to gather the information. Author Amit Lohia takes a look at how sp_spaceused works and how you might customize it to suit your needs.
2005-06-23
13,468 reads
SQL Server 2000 does a lot of things for the DBA, tuning, updating statistics, scheduling tasks, wizards and more. But one thing that it does not help with is choosing the correct data type for your data. New author Amit Lohia brings us a technique and some code that will examine your existing data and suggest places where another data type might be a better choice.
2005-06-06
10,372 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
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....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
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