This is sp_spaceused for the biggest table:

name, rows, reserved, data, index_size, unused

mytable, 38380502...

I left few gigs in the files, besides, after dropping all indexes, there were even more space, but when I recreated the first clustered index on the biggest table, the...

No, it did not work, on step 4 the files grow again for some reason. 🙁

Thats fine, this is a one off operation anyway. So the plan is:

1. Shrink the files to just over the minimum size.

2. Drop non-clustered indexes

3. Drop clustered indexes

4. Re-create...

Eureka! I should just drop the indexes and re-create them and then only re-index the current partition!

😛

So there is no way to rebuild the indexes without blowing out the files? What that SORT_IN_TEMPDB option is about then? Isn't it supposed to prevent the file...

Ok, I've got over 50GB of space in those older files, which I need to recover. If I shrink the files, I willl fragment the indexes. If I...

How do I recover the space then? The older partitions do not change, so I need to shrink them and then rebuild the indexes without blowing out the files...

Ran this:

ALTER SERVICE MASTER KEY REGENERATE

Changed the service account to the domain account using SQL Server configuration tool, but the SQL Server service would not start.

Any ideas?

The only difference I could find, was that in test the dev account owns its own schema (Mydomain\myaccount_dev) and has it as a default, while in prod, the prod account...

The domain group membership is complicated, but there are no direct permissions on the SP and on database level I could not find any group, that has permissions to...

Already done this. I was just wondering if I could do any better with the trace.

So, I guess, in case it is unique, you can only partition the table by one of the columns present in the clustered index... 🙁

Found it out!

"sp_configure [filestream access level], 1" only changes the "config" value, not run value, so sql server configuration manager should be used to finish the configuration.

This is the same. If you specify "norecovery" option...