When creating the tables, prefix them with

"dbo."..   EG, "create table dbo.myTable" rather than "create table myTable"

The thing with indices is that they help SQL server perform its work efficiently (clustered or non-clustered) - They *should* have no impact at all on the data you receive,...

Yup, I agree with Phil...

Two ways around this - use a stored proc to encapsulate the logic...

OR

Have some sort of "messageLog" table - when you send a message, first check...

Read from about half way down this link

http://www.sql-server-performance.com/performance_monitor_counters_sql_server.asp

Talks about what your latch waits are, and how it can be either memory or IO that is causing your messages...

Google -...

The ufortunate by-product of this (and I have a few procs like this too) is that SQL cannot effectively use indexes.  I've coded mine using Vladan's suggestion which is probably...

I know that a lot of people (and one day I might give it a go) use code generators to generate a lot of the boilerplate code for insert/update/select stored...

Doesn't the cursorOpen proc call give you the code for the select statement?  They are using server-side cursors - perhaps if they used client-side cursors things might perform a bit...

So you can log in using

server=(local),  user=myuser,   pass=myuser

when using VNC, but this fails in a Citrix session?

Hmm - What if you specify the servername in the VNC console session -...

As someone said, ISO format should also work (yyyymmdd), but the ODBC format should also work everywhere - it is something like {t'yyyy-mm-dd'} - can't remember off the top of...

I have had the same thing happen (packet size + fragmentation) on some VPNs before...

Lowering the MTU should help fix that.  You could also try to fiddle with some of...

Fair enough - more than one way to skin a cat   Just make sure you document it somewhere.

So the 2GB limit in MSDE (2GB data + 2GB transaction) is now 4GB in Express (4GB data + 4GB transaction??)...  Are you sure the 4GB is not 2GB +...

To overcome this, you could always import the data into some sort of staging area, let the user manipulate it (all with tiny transactions - it's just their staged data - no...

Are you executing from Query Analyser, some database API, via OSQL, etc?  Perhaps your connection library is overriding some of your parameters.  I've always found the yyyy-mm-dd format to work...

You can spool the data to a temp table (of the # or @ variety) - this lets you do whatever you wish with the output of the select statement.

You...