Vika (9/5/2008)

---

And another question. If log is full and so huge that there is no space to back it up, would it help to shrink it first and then back...

In the test I posted the variations were indeed completely random. I'll test later with a couple of...

You can load the traces into a SQL table (profiler -> save to table or fn_trace_gettable) and then you can query them in SQL. Easier than analysing in profiler.

Database corruption. Do you have an up-to-date backup?

Please run the following and post the output.

DBCC CHECKDB ( < Database name > ) WITH NO_INFOMSGS

Depends. TempDB's used for checking indexed views as well. Probably other things too.

Ummmm.....

Which of these inserts is throwing the error? (in management studio, if you double click the error in the results pane, it will take you to the line in question)

What...

Usually hardware.

http://www.sqlskills.com/blogs/paul/2008/08/27/SearchEngineQA26MythsAroundCausingCorruption.aspx

Honestly, in my opinion, if you do your job right on the SQL syntax, DB design and indexing a NOLOCK statement shouldn't be necessary in any environment.

If you're encountering severe...

Glen (9/4/2008)

---

Gail,

would it be then proper to consider that on a table with search on an unindexed column the

'WHERE @param = something or field = @param" and

"WHERE field = @param...

List all but the one or two columns you don't want. Even when you do want all the columns it's better to specify the names explicitly. The table may get...

I had a dev that wanted to use the LOOP hint...

It can 'short-circuit' but not on the basis of where the expressions are in the where clause, rather which indexes are used and which expressions those indexes can 'evaluate'

If we...

Won't make a difference. Order of clauses in the WHERE are...

Depends. Does you app need/use 48 GB of TempDB? If yes, then it's not too much.

48GB isn't large for a DB.

You can start out with just 4 files and then...

If you know that a set of tables are static and hence locks are an unnecessary overhead, then put those tables into a separate filegroup and mark that filegroup as...