Try this:

declare @startdate smalldatetime

select @startdate = (Select max(Date_Idx) from dbo.DimDateLM where Date_Idx < '2079-06-06')

set @startdate = dateadd(dd, 1, @startdate)

while @startdate < '2032-01-01'

begin

    insert into dbo.DimDateLM set

        Date_Idx = @startdate

    set...

As this is SQL 2005 (based on where you posted), try putting your hefty query as a CTE and using that in your query.

I had the problem here with QA and SQL Server 2000.  Our network has had issues most of the year for reasons I won't go into that has caused connectivity...

Or, if you know your data, you could build on this:

declare @varTable table (

    TestData varchar(max)

    )

insert into @varTable values ('Dtautas2/22/2007 5:22:32 PM: text')

insert into @varTable values ('Dtautas2/22/2007 5:22:32 AM:...

I have also experienced this on occasion where I work.  One of two things has occurred; first, the server running SQL Server has been rebooted; or second, we have had...

My question is why?  SSIS has a data conversion task that you can use to complete the data conversions you require without writing any scripts.

I am going out on a limb here, and say you probably need to rebuild the master database so you can start SQL and restore the backup of the most...

Not sure, and don't really want to get into a religous data warehouse discussion, but I think you have the data warehouse approaches flipped.  Kimball talks about a Data Bus...

SQL Server 2000 does not allow you to use a variable in the top statement.  SQL Server 1005 changes that.  In SQL 2000, to be able to specify a different...

There really is no protection from mistakes, only ways to slow you down when making them.  In SQL Server 2005 you can setup DDL Triggers that would prevent things like...

That helps.  It means that products like PeopleSoft aren't going to update their tools to take advantage of non standard enhancements like the INCLUDEd columns in indexes in SQL Server...

First, your UPDATE syntax is incorrect.  Second, if DUEDATE is a calculated field, it can't be updated, the fields that make up the calculated field needs to be updated.  If...

Don't double the size of the field: MyCharField varchar(25) --> MyCharField nvarchar(50) NO.  It simply goes from MyCharField varchar(25) --> MyCharField nvarchar(25).  The change will double the amount of space...

What doesn't make sense?  Tell us what you think you understand (or don't) and then we can fill in the blanks and increase your understanding.