Checked this today on SQL 2012 sp1.

Its now capped at 2 TB.

For a fix you can run the following commands from an administrative command prompt. Locate this directory: %systemroot%\system32\wbem

Run these commands in sequence & restart your setup.

regsvr32 cluswmi.dll ...

Trying to keep it as concise as possible.

Hey - Jon, how did you verified that was problem with the object ?

Check this

http://social.msdn.microsoft.com/Forums/en/sqlnetfx/thread/4a032c4b-1402-4c53-b34e-8c8bd724f904

try cmd shell & run

wmic cpu get numberofcores, numberoflogicalprocessors

Thanks Tim, I'll add those in the next update.

The command is DBCC TraceStatus.

You can details here

http://msdn.microsoft.com/en-us/library/ms187809.aspx

Hi - this is kind of a late check,...

AN update from MS

http://connect.microsoft.com/SQLServer/feedback/details/753184/sql-server-transactional-log-file-ldf-having-a-2-tb-limit-wrong

I'll be dropping this mammoth DB today.

Hey thanks for the inside peek, let me know if you are able to get the attachments.

How it started?

Initially it came out of a practice where my PSH program will collect the tweets & push it into a table, the DB & LOG auto file growths...

Yep though've used those but was looking for an easier way, in lots of cases with me mostly on SQL 2000. I'm seeing a difference in sysaltfiles & sysfiles not...

Any other quick way by reading some specific page / headers?