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,720 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,706 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,533 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,400 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Helping an English Student with...
Comments posted to this topic are about the item Adding Bits I
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers