This is espicially why you should always list the columns one by one in the statements. If this is production code and that the column order rechanges for any...

I don't have any experience with that. But you don't have to supply the owner. I have a link server that I Access like this :

Select *...

Just give me a few years Frank and I'll join in on that competition .

Congrats on the MVP title.

Here's a search sp that I made using a few cases

CREATE PROCEDURE [dbo].[SPNSearchClients] @FacturerA as varchar(10) = null--# Facturer à

, @Location...

There's already a script posted that does exactly that, so I won't repost.

have you tried to use it in a four part naming :

Select * from Linked_server.database.owner.object

What error are you actually getting?

It's hard to point you in the right direction because the browser is removing some of your code.

However can I assume that you have 2 recordsets opened and that you...

ya the problem comes mostly for table updates that are recreated. but for simple things like this it seems to do the job right.

That looks great.

You can copy dummy files to a test directory with different create dates. Then copy this code into a .VBS file (notepad, save as txt and rename...

NP.

Give a guy a fish and feed him for one day, teach him to fish and feed him for life. :-).

(I know it's cheesy but it's still true).

I'd use ainsi compliant syntaxe but that's gonna do it :

UPDATE a

SET a.called = b.called

FROM t_ORDERTEST a inner join t_ORDER b

on a.id = b.id...

Just go in EM, add a default constraint on an existing column and see what code is generated.. it's gonna look something like this :

ALTER TABLE dbo.TableName ADD CONSTRAINT

DF_ConstraintName...

Can you post the solution so that others may profit from your experience?

I already tested that theory, and there's no speed difference between select * and select 'x' and an exists statement. The function just returns true without trying to figure...

Please make sure you read my link before going down that path. You must make sure nobody besides you can access this proc (or at least only trusted developpers).