You can query sys.databases, or you can use sp_MSForEachDB.

You could use CLR instead of xp_cmdshell. You could use a job that calls the command line. Either will work.

I don't think you'll have to change code at all. That's kind of the whole point of partitioning a table.

Test it in your Dev/Proof of Concept environment.

To expand on the "discovering what we already know" point:

A company I used to work for knew that a lot of time was being wasted by back-and-forth between Order Fulfillment...

I'm not clear on what you mean. Do you mean you want to get rid of the accents on characters, or are you having problems with accents going away...

Here's a reasonably performant version. Assumes you have a Numbers table. If not, search for Numbers table and Tally table, and you'll find how to create one, and...

There's a slim but real chance of hash collision, even if the data is different. What will you do if that comes up? Just hope it doesn't?

Chris Morris-439714 (12/3/2010)

Hey Gus, reckon...

Why would you bother? Use the Where clause. That's what it's there for.

select *

from dbo.MyTable

where @Parameter = 'A'

or ParentTradeID is not null and @Parameter = 'O'

or ParentTradeID is null and @Parameter = 'R';

Wouldn't that do it?

If you're using SQL 2005 (as per the forum you posted in), then you do a two-state "upsert", which just means you do an update on matched records, and then...

Paging functions in queries can be a bit of a problem.

Are you using SQL 2000, as per the forum you posted in, or is there any chance you're using 2005/2008?...

Can you just use a LEFT() expression on each row, up to the first comma?

Are you absolutely certain the pipes at the beginning of the row don't mean the first column is empty/null? I've seen delimiters do that before, in that case.

You'd have to reinstall as the default instance, so far as I know.