GilaMonster (2/28/2013)

---

You don't need to correct the situation where one of more of the files has expanded because on restart of SQL the files will be back to their defined...

So you don't use a startup proc to verify tempdb data files are all the same size and sync them if they are not?

How, then, do you become aware of...

Jeff Moden (2/26/2013)

---

Just to emphasize the performance differences between using a string conversion or not for date conversions, let's do a little test... a race, really.

Here's the test data. ...

Robert Davis (2/27/2013)

---

ScottPletcher (2/27/2013)

---

If a tempdb data file is 1.5G when SQL goes down, won't it be 1.5G when SQL comes back up? Isn't it automatically reset to its...

Maybe it's just an issue I had.

The last time I altered the SIZE of tempdb data files in SQL, when SQL restarted tempdb files were still larger than that.

If the...

Robert Davis (2/27/2013)

---

NEVER manually shrink tempdb files. It can corrupt the tempdb files. Avoid shrinking files of any...

Robert Davis (2/27/2013)

---

NEVER manually shrink tempdb files. It can corrupt the tempdb files. Avoid shrinking files of any...

GilaMonster (2/27/2013)

---

ScottPletcher (2/27/2013)

---

Then, set up a start up proc to shrink both tempdb files ... I'd say to 1G each, so you have some cushion. You really don't ever...

Hmm, now that the db is in recovering status, you may not be able to (temporarily) add another log file on a different drive to allow the db to keep...

No,...

If XACT_STATE() returns -1 [uncommitable transaction], you can't do anything else except rollback the current transaction. That is a logical restriction within SQL Server itself.

In that case, you would...

Look into clustering the table on column A: that will likely address the issue more effectively and efficiently than a slew of nonclus indexes.

Yes, add a new tempdb data file, at exactly the same size as the current data file. Use KB to get the exact size. [That way you will...

Here's a quick script to demonstrate the warning and then the actual error that occurs:

USE tempdb

CREATE TABLE test_index (

long_column_to_index varchar(8000)

)

...

appClinic is the only column(s) that is(are) longer than 900 bytes.

If the total bytes in the index keys are 900 or less, that's not an issue for SQL, so you...