Don't get caught up too much in the R5 penalty. It certainly is a bigger hit than R1/R10, but I've run SQL Server databases for years on R5 and it...

You need...

Ray K (10/21/2013)

---

Oh come on!!!!!!!!!!!!!!!!!!!!!

Andrew Luck has a good day -- and the rest of the team -- pretty much the entire team -- goes in the tank!!!!!!!!!!!!!!!!!!!

(throws up hands...

Thanks, I'll take a look next week

Do you need to retrieve the numbers? If not, you could hash them, but again, as Sean suggested, do this in the application.

SQL 2000 has limited options. SQL 2005+ has...

It doesn't affect the database, but if the space is needed, the log will grow if autogrow is enabled, and stop accepting transactions if it isn't.

The size of the log...

When a login is disabled, sa or otherwise, it can't be used to log into the system.

enabling it to change the password won't do anything to the server, however if...

The transaction log is important. Without it, my system stops. R0 isn't acceptable for me.

Not sure what R5 + a spare is, but I'd just have one spare in the...

If the offsets are 31-32kb, you're misaligned.

You need to reformat the drives with the offset to match your stripe sizing.

arosenbaum,

People are willing to help you, but we don't know your environment, your data, or anything. In order to make it easy for us to help, provide the DDL for...

You can add another log file to the filegroup.

http://technet.microsoft.com/en-us/library/ms189253.aspx#TsqlProcedure

In that case, follow Gail's advice. Record the peak log usage and shrink to that (leave a pad).

You'll have to provide some code and perhaps an execution plan to understand what you're doing here.

bcp will do a csv export of data. That should work.

If you can select the data in SSMS, you can save the grid results as a csv as well.

You are performing log backups, correct?

These help manage the size of the log.