Steve Jones - Editor (1/7/2009)

---

I used to see those in NC, Brew-Thru's. Literally a large building with a garage door on each end. Lined with coolers, you literally drove through...

Andrew Gothard (1/7/2009)

---

NB. This is not covered by

RAID 1 - as proved recently

or

The directories holding the files are backed...

I was under the impression that WITH RECOMPILE didn't work really well at the PROC level in 2005. Once they switched to statement level recompiles, the proc-level one didn't...

For what it's worth - I'd also make sure that this "user ID" is NOT your actual primary key. Because it carries "user significance", and like Jeff pointed out,...

I suspect that database is running in Comptibility 80 mode, because I've run scripts substantially larger than 8K in a nvarchar(max) variable with NO issues (130K was the biggest one...

I would also make sure that all of the tables involved are aliased, and that all column references have a matching table ref on them, so that there is no...

It most like has to do with the Substring function in your where clause. This forces the DB Engine to have to scan through everything looking for matches, and...

I would leave the identity column to do what it does, using it as the "internal key" in relations, and have a "surrogate" or external user key in the form...

I didn't recall Terminal Services being a separate install in 2003. I thought it was simply a feature to enable as part of Windows components. As such -...

some of the premium FTP clients (like WSFTP) have a ftpsynch utility, which will push everyhing, building the remote structure if need be. Well worth the 39$ if you...

What are you passing as @sortexpression? Looks to me that you need to make that bigger and change what you are putting in there, because that is what is...

If your stored proc doesn't lend itself to being re-written as a function, you can always look at using a self-referenced linked server set up. Meaning - set...

Sounds to me like any of the following would work:

- Crystal Reports Server and/or a businessObjects Universe with the appropriate permissions set up

- the Post SP2 SQL Reporting...

You should probably start by taking a look at what security mappings were set up in the linked server object. If everyone is getting that message, then it is...

make sure both PC's are using the same client protocols (under SQL Server configuration Manager).

Also - is the SQL browser running?