Do it in batches of a few hundred thousand rows at a time. If you do that as a single statement, the log must be big enough to contain the...

Not that I'm aware of.

There is a traceflag that, if enabled will allow SQL to store files on the network, but it is strongly not recommended. Files on the network...

You cannot put SQL's database files onto a network drive, regardless of whether you create a mapped drive or not. Files have to be on local storage, SAN storage or...

That kind of error can affect just about anything. It's saying that something is changing SQL's memory outside of its control.

Are you the DBA? The checkDB errors aren't severe...

Not possible. SQL will not allow its files to be on a remote drive. The network file-share does not provide the IO guarantees that SQL requires.

You've either got bad memory or there's a memory scribbler somewhere (kernel process or something in-process with SQL that's changing SQL's memory)

To say this is bad is an understatement. It...

If you're requesting all the rows, all the columns from a table there is no practical way to optimise the query. It may take some time if the table is...

Indexes in general are not for referential integrity.

Foreign keys are for referential integrity.

Check constraints are for domain integrity

Primary keys (not...

LutzM (8/16/2010)

---

There are several options I can think of:

1) Analyze the index job if it can be optimized (e.g. only roerganize/rebuild indexes that need to be touched basd on fragmentation...

I'm not sure I follow you completely.

As for your example query - select * from table - there's no way to optimise that. It's asking for all rows of the...

Yes, and it's true for the clustered index as well. Indexes don't prevent values from been inserted. A...

No

Question: What kind of latch does SQL Server use when reading a page from disk?

Answer: Anytime...

Why would you put the column Date into the index?

Don't change the system tables. They are not there for you to mess around with. Leave them alone unless you're happy with possibly ending up with a corrupt and unusable...

Latch_ex is not an IO-related wait. The IO-related latch waits are the PageIOLatch waits. Latch_ex is a non-buffer exclusive latch, meaning it's not related to pages.

From a kb article...