Dwain - that's impressive! I'm going through it now to see understand what's going on here.

Jeff - I've checked with the data sourcing team - they have told me...

Eugene - Max size for Value1 is 7 chars and for Value2 is 10 chars.

Cadavre,

Sounds intriguing! Look forward to seeing what you can come up with tomorrow. FYI, the numerical input is always a positive absolute number.

Thanks,

Martin

Hi Eugene,

Thanks for taking the time to reply.

You are right, it is too big for a bigint if I use that method as the two values can be quite long.

Sean...

Hi Sean,

Yeah, it does sound like a strange request, but I'm working for a bank and we have historic data in all sorts of wierd formats. It's not an...

I remember the days when it was possible to look at the anwer for yesterday's QotD, change the querystring (subtract 1) to get back to it again, then answer it...

1) Plugging a USB stick into the back of my laptop only to lift the front of my laptop to put it away and bend \ break the stick.

2)...

One observation; you aren't creating a primary key on this table (and presumably any of the other one's you are creating). When you create a primary key, SQL automatically...

The testing for this upgrade started a good few months ago and at that time SP1 was just a little bit too new to apply to the new environment. ...

In addition to the above, I would take a look at the waitstats. When a query runs, it will at some point be waiting for someting - disk io,...

You haven't suggested in your post that you've actually done the upgrade yet - just ...

I ran the SS "Best Practices" wizard and the "Upgrade Advisor". Then I went to...

I am with you on being reluctant to shell out for Ent licenses, especially as you are working on an archiving process.

Is is necessary to reindex every index on the...

There is a useful free tool that might be able to help you with this - it's by Quest software and available here - http://www.quest.com/discovery-wizard-for-sql-server/.

The only drawback is...

Once you've removed all the cursors, the next step would be to break the stored procedure into 'chunks' and run each bit individually. This will allow you to identify...

I'm back off my hols, and raring to go again.

Out of the three suggestions here, I've tried two of them. Sadly, the 'drop & recreate' idea failed to make...