Even more important....DON'T try to run an EXE via a SP.....you're lining up some bad problems for yourself.  SP's can't run/launch interactive EXE's and you could overload your server.  I've...

In Ireland (and I think the EU), if you are obliged to use a monitor for work, then your employer is obliged to contribute to an regular (bi-annual I think)...

There's a generic cross-tabs query available at http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=6216

The code has been improved in several later iterations (so you may need to work backwards), and has some limitations, but it...

Given the comical data designs I've seen at work (and here).....I'm surprised somebody hasn't made an emoticon linking the character and the work....!

varchar or nvarchar?...only the latter can store unicode characters.  search here (and other reputable sites) for "sql + unicode + translate" or "sql + unicode + japanese".....others have come across...

Why not forget about the mystery stuff.....move the db's to a clean server.  scrub the dodgy one and swop the clean one back in.  I know solving problems is great....but sometimes a...

re "http://www.dkranch.net/images/steve/khali_dad_c.jpg"

I'm not sure who's winning that argument.....or which direction the wrap/roll is going!!!

There is an issue (bug) with "SELF BLOCKING" which arose with either SP3 or SP4 of SQL2K.  Search here (or sqlteam.com) for info on same.  A patch is available.  Paul...

the following may be of use to you.

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=57242&SearchTerms=longitude,latitude,zip

"Parameter sniffing" may also be at play.

Search (here and elsewhere) for an explaination of the term and a simple remedy.

"why is that?"

Less empty space to search over to find the real data?

Less head-movement of the disk spindles?

Better organised data - contiguous instead of randomly ordered.

1. clear out test tables of all data.

2. establish building block tables...ie the parent tables in any parent-child relationships.

3. dts the data over from oldserver to newserver in the order...

While you have described your environment very well, one thing you left out was the current size and planned growth rates for your databases...it might matter somewhat

This is a symptom of either the wrong backup strategy being in place, no backup strategy in place or the wrong 'failure recovery' model specified for the DB.  The solution...

parse the string (looking for the indicaters as to where the h + m bits are) and use the numbers extracted in the formula (60*hnum) + mnum.

you will need to...