That was funny... thanks for the laugh.

By the way, jesus is dead and did not live in the 20th century.  Influential in the 20th century ... maybe.  Alive in the 20th century ... definitely not.  Now,...

No particular order here either:

Doyle Brunson

Antonio Estfendari

Phil Ivey

Phil Lak

Phil Helmuth

Johnnie Chan

Scotty Negyun

Daniel Negraneau

Scott Fishman

Chris (Jesus) Ferguson

easily done... just configure each instance with 2 gig via sp_configure

I've encountered this issue.  You cannot have print statements in a stored procedure that returns a recordset to VB, otherwise the recordset will be returned "closed".  Try removing the print...

There is a "boolean" data type - it's the "Bit" data type. 

Instances can only be created upon install.  Thus I think you are left with 2 installs to do to accomplish your goal.

Sometimes these things just happen, sometimes they are signs of bigger problems to come (failing hard drives, etc). 

In my 8 years of dealing with SQL Server, I only ever...

I assume you've tried:

Use master

DBCC CHECKDB

GO

Sounds like your master database is fried somehow.  You might want to think about rebuilding your master database.  Do a search in BOL for Rebuild...

The error log was complaining about DBID 1, this is the master database.  Run DBCC CHECKDB against that database.

Did you grant exec privledges on master.dbo.sp_sdidebug to the login attempting to do the debugging?

Be warned that using the T-SQL debugger will cause major blocking issues.  It's a common practice to...

I can't tell you anything about the real-time monitoring tools.  But I can tell you that Litespeed and SQLCompare are both well worth the $$.  They've both saved countless hours...

DBCC CHECKDB

did you run dbcc checkdb on master? 

When a database is set to autogrow - that's what it does.  It's autogrows the file(s) as nessecary.  It is not needed to increase the size at this time.  Although...