Search results for query: *

I found it. DBCC TRACEON (3604); go dbcc page (db name,1,9112,3) This tells me the object id which I then looked up in sys.objects

Hi All, It seems this error may imply I have some corrupted page. But how can I use the page id in this message to track down the table? It occured during a read of page (1:9112)

Oh yes, it definitely auto grew until the Data file ran out of space. BUT, the process also had TempDB data up to 230GB and that is on the same drive. So, I guess I am wondering if the index creation can be made to not use so much TempDB?

I attempted to create a huge index on a view and it failed after 16 hours. I expect the indexed view to be about 200GB and I had about 300GB available. It failed because the DB ran out of space on the drive, autogrowth is set to ON. This is SQL 2005. Is it true you need twice the space for...

thanks. THat was not quite what I was looking for but you pointed me in the right direction and I have figured it out now.

Seems simple enough, but I can't figure it out. SQL 2005 Table A load_date - pk company_id - pk Table B business_date month_end_flag I simply need to write something that will copy over data that is greater than 120 days old...but not any month end data. Once copied to another table....table...