Mike C (3/6/2008)

---

Yes, catchy title. When I first clicked on it I actually expected it would be about the type of file I was asking about. The author's...

I don't believe it was meant to... wasn't advertised that way except maybe by a slightly misleading title.

Very cool... thank you for the stats and the feedback, John.

That's useful... thank you very much.

Yep... I gotta agree with that. Like I said, it's the classic solution and it's pretty darned fast to boot. And, like you said, it works on both...

Why shore'nuf! 😀

You know... you're absolutely right... if the original requirement was to return ALL columns and ALL rows for ALL...

Sure am sorry about that... Task Pad has always been a little quirky in 2k.

If you really want to know those values, try the following

USE TEMPDB

EXEC dbo.sp_HelpFile

EXEC dbo.sp_SpaceUsed

Grant Fritchey (3/6/2008)

---

Jeff Moden (3/6/2008)

---

Ummm... I gotta say, "Not always"....

Heh... dang, Doug! You fit right in with me an all the other crazies 🙂 ... and it didn't even take you...

Make that 3... it looks like they also fixed the non-wrapping problem on long thread names!

Jeff Moden (3/6/2008)

---

The following is a test to see if SSC-475 has been resolved...

DROP TABLE mm_CompanyNo

DROP PROCEDURE GetNextCustNo

GO

--==============================================================================================

-- Setup for the test

--==============================================================================================

--===== Create sequence table...

Nah... they need an absolute Ninja, Sam... they want to let everyone run rough shod over the database and the server but still keep it running. They need to...

Jacob Luebbers (3/6/2008)

---

Cheers Jeff! There are quite a few articles around that simply say "don't SELECT... INTO... a temp table" without qualifying it with "but only really a problem...

Most people use the default settings for auto-grow and DB size... that's 10% and 1 MByte. Now, lemme tell you why it's REALLY bad to do that... first, what...

No offense... but this isn't really something that someone "new to SQL Server" should be asked to handle. You need to hire a good DBA to help you do...