Nice one Jeff - I can see it's been a little while in the making (given all of the handy graphics...)

You might care to edit your first post in this...

Don't forget...

Try doing the attach from within SSMS (or in your case SSMS Express). Once you add the main MDF, but before you click the attach button, you will get...

Same version as yours, and the tables open up...

I'm thinking it's file specific... maybe something in the files it just doesn't like... ugh.

Jeff Moden (12/5/2007)

---

First thing I'd try is to recompile all the views involved... could be you have a bad execution plan cached up somewhere.

I've run into this problem with "views...

I did it several ways just to make sure it IS a v.97 file:

- dusted off some of my old FLOPPIES (yeah - I had to remember what they...

ISNULL(a,b) is a function. It check to see if A is null: if it isn't - it returns A, otherwise B. I was just using it as an...

I made an assumption as to what kind of data @franchise was. if it's supposed to be some kind of string, put quotes around the -999 (both instances), which...

Steve Jones - Editor (12/5/2007)

---

I tend to agree with Wayne. I think it's not necessarily in their interest. They certainly don't want to deal with customers getting shut off and...

I'm sure I know the answer to this...but there's no chance of maintaining a "most current" boolean flag on the security prices, correct (after all - you don't seem to...

I also just came across this new little feature in 2005, which allows the file to grow WITHOUT zeroing everything out. It's got some security concerns, though, so you...

Oh it probably won't take a LOT of time, but it should be really noticeable for a while (20-40 minutes depending on your data subsystem from my guesstimates, longer...

No - not like that.

CASE is used to return single scalar values, but not to add clauses to a SQL statement (or to add to a clause).

You need dynamic SQL...

It will force the DB to grow right then and there to 250GB... You're going to want to do this during some down time...

The merge joins seem to be killing you. They're occurring because of the "many to many" merge joins, which are causing multiple (apparently very large) worktables be created in...