running on SQL 2025 build 17.0.1105.2 throws an error for the union and collection aggregates, but finishes without a problem.

Could not find method 'UnionAggregate' for type 'Microsoft.SqlServer.Types.SqlGeometry' in assembly 'Microsoft.SqlServer.Types'.

I found this in BOL April 2006.

By default, the image is rendered in TIFF format, which can be displayed with the default image viewer of your operating system...

A first palce to look, besides system and application logs is sqlsp.log - which should be located in the windows directory on that machine. Look for error messages in there...

Your most likely looking at seconds expired since '01-01-1970' in case you want to 'translate' into datetime you can write it like this

SELECT 

DATEADD(ss, (A.[yourtime]- 14400), '01-01-1970') AS [UTC-4] --...

I hope you mistyped/misspoke and didnt compress the log files via ntfs or any other method. A) it's not supported B) Your log files absorb the majority of your I/O activity...

Thanks for the follow up Vincent. I understand your earlier statemet now given the added explanation/observation.  - Sassan

I typically take SQL server offline - in case this is not possible - you can detach certain DBs at a time in case they are located on separate drives....

Could somebody explain the math for 58 records should take less than a second at 100 Mbps - Thanks already

Are the new drives manged by Vertias volume manager?

I can't seem to find either the download or DBA_Verify_File_Exists procedure.

As a safeway out for future questions - one answer possibilty could always be 'none of the above'. Who said multiple choice has to be limited to 4 or 5...

you probably attached msdb back before attaching model back. In this case add startup traceflag -T3608 (to only recover master db on startup) then detach msdb. Accordingly you would now...

Several aspects stand out. Your collation is Thai_CI_AS which might add addtional overhead (double byte for unicode?) (I am assuming your whole server is in the same collation. Your temp...

Temp DB is in simple recovery mode - accordingly truncating the log is unnecessary.

The error message you got indicates that the Default file group (Primary) was full - this indicates that tempdev (tempdb.mdf)...