Craig Farrell (3/17/2011)

---

Generate a new filegroup, move *everything* into the new filegroup. Rebuild the original Primary as desired, move everything back,...

Craig Farrell (3/18/2011)

---

alexus8888 (3/18/2011)

---

We got a 20% improvement in an ETL process by creating the filegroup with 4 files all on the same drive. didn't believe it myself till I...

rollback -

dbcc shrinkfile with the emptyfile option, followed by alter database command to remove the file.

- or restore from the backup you would of course take before doing this, but...

Craig Farrell (3/17/2011)

---

george sibbald (3/17/2011)

---

Userdb.

don't quite understand why myself, but as disk technology moves forward old truths can become outdated.

I still would not recommend it as a default approach to...

Userdb.

don't quite understand why myself, but as disk technology moves forward old truths can become outdated.

I still would not recommend it as a default approach to file layout, and have...

please don't hijack threads. start a new thread with your question if you want help.

nice answer on the SP application by the way. I would add ensure any server level...

Is this on a SAN? Are you looking for performance improvements in reads or writes? speak to your Storage people. Depending on the exact configuration you can see improvements because...

here's some code what I pinched from somewhere -

--How to isolate the current running commands in SQL Server. This query isolates the SQL in the batch

-- actually running...

root cause -

After speaking with Diskeeper they advised us to install Diskeeper 10 version 14.0.913 which it the latest build, we have installed this and retested and we have...

thank you Gail, some definite similarities there, especially in the 823, 8966 errors and apparent EOF conditions. Main difference was my databases WERE actually corrupted.

I will pass this on to...

thought I would feed back on the root cause of this.

Investigations of the disk showed no errors on the disks, which is unusual for an 823 error but there you...

make sure you use shrinkfile not shrink database

try the truncateonly clause first

other than that you have no choice but to do it in chunks, best to do that anyway as...

run this search on http://www.google.com/microsoft

service pack 3 sql2005 cluster

and select instructions that apply to you.

basically stop connections, backup databases, disable ddl triggers, apply to active node from a location both...

yes you can.

logshipping is at the database level and the database is not changes by 32bit or 64bit.

question specifically mentions SQL2011 (if it will be called that.)

SELECT * FROM ::fn_virtualservernodes() is only there for backward compatibility and should not be used. It works all the way up...