I needed average run times of all ETL jobs in the last 6 months and this was perfect. Thanks so much!!

Related Q.

Where should we *not* find 2147483647 in SQL?

An interesting number! It even has its own Wikipedia page.

@duran-2 - you are welcome , just paying it back to SSC 🙂

One other resource worth mentioning is the MS Learning channel. Each of the SQL 2012 exams...

Thanks for encouragement but it will be a few months before I study again in earnest.

I started with Andy Leonard's excellent 'Stairway to Integration Services' here on SSC:

http://www.sqlservercentral.com/stairway/72494/[/url]

Also James Beresford...

Not good, failed with 610. That's 610 on the SSIS Section (got over 900 on the Admin Section).

25 questions on each section so not a lot of margin for error....

The phrase here is "Cumulative Updates". See here.

So after each Service Pack for the relevant platform, install the latest CU and you're bang up to date.

A full transaction log is not good, see this[/url].

Sort this out and the replication should recover. If not setup replciation again.

Try and connect with a dedicated connection (DAC) and run the failing script again:

sqlagent100_msdb_upgrade.sql error /[/url]

Excellent article and one to add to the toolkit. Many thanks Paul.

"A table does not so much have a clustered index as a table is a clustered index. "

Thanks, this is a nice (and memorable) way of putting it.

D'oh!

SQL Express 2008 will auto pick up 2005 SQL instance and ask do you want it upgraded it or just install a separate 2008 SQL Instance.

http://msdn.microsoft.com/en-us/library/ms143393.aspx

http://msdn.microsoft.com/en-us/library/ms144267.aspx

In my situation I'd expect the space freed not be reused. As I mentioned I don't think my sitiation is typical!

In any event - an eye -opener for me...

I'm the OP and it seems my situation is not typical.

The database is used for syslogs. Data is periodically truncated from tables and this leaves a lot of free space.

I work with a database that often shows up to 50% free space, shrinking releases space but thanks for the replies!

Are you doing an in-place upgrade? I assume not. I haven't done SQL 2000 -> SQL 2008 but have done SQL 2000 -> SQL 2005.

Back and restore (and check compatability...