Ah, my bad.

It's not there. I confused myself with OSQL parameters...

Still, the mainproblem seems to be scope.

I'll see if I get some...

I didn't? Thought I did..

> Best practice #1:

> Always use objectnames that *don't* have to use square brackets in order to not crash your code []

If this was unclear, the intended contex with...

Good catch.

Didn't think of recovery model playing a crucial role..

(need more coffee...)

/Kenneth

Jeff, I thought so as well at first, but that's not it.

A tablename with just one char will be substringed as that single char..

(hint - quotename)

Well, you could look at the difference between UC and UI as 'labeled' or 'unlabeled', if you get my meaning.

When you declare a UC, it's the declaration, literally, that differentiates...

The thing about the 'best thing' is that in order to determine that it really is 'the best', you need something to relate it to. That is, a context.

Also, 'best'...

I think Noel pinned what this confusion generally is about..

There are two sides: Logical and Physical.

Per se, a constraint has nothing to do with an index, whatsoever.

As Noel says, a...

Not necessarily (could be 4, 5, 6 also)

Since it's depending on the setting of @@DATEFIRST (which may change/be different), the 'safe' way would...

Looks like this isn't something that has to do with 'traditional' data.

The table with formulas is just a place to store formulas, instead of having them coded in some app.

The...

Agreed, this is important.

As Jeff says, this is potentionally a timebomb waiting to explode...

/Kenneth

I guess I'm still missing out on something...

Are you saying that you in your local (copy) tables from time to time insert your...

Well, let's put it this way then.

'Best practice' (as far as naming conventions go) would be to use names that won't rely on either square brackets or quoted identifiers, but...

And since the copies are just that - copies, you shouldn't have the identity (auto incerement) property in those tables either. If you remove that, and keep them as regular...

You need to use a tool that can read the transaction log then.

There are a few different out there.

The other option is to restore your database...

/Kenneth

Given the example, it looks like you need it just as written.

(in any case an IN clause is expanded internally to OR's anyway)

/Kenneth