If I repeat the same derived table 2 or 3 times in my SQL select statement, the execution plan looks like it executes the same select code several times.  Do...

I have usually steered clear of Access, but I believe that a text/memo field in Access can grow quite large - hence it is more like a text field in...

or a classic after trigger on the table containing the foreign key - it can do a quick select to check if any rows are being inserted (or updated -...

Cheers for that

Actually, there is an FAQ on this site that deals with something quite similar to your problem.  Visit:

http://www.sqlservercentral.com/faq/viewfaqanswer.asp?categoryid=3&faqid=364

As an aside, I've been a member here for a couple of...

You could consider writing the query using an outer join (to keep your last null row) to join the table to itself (alias it as TransferFrom and TransferTo) with the...

It'd be nice if there was one in brisbane

Excellent article.  I had heard of the terms before and had "one day" planned to read up on them thinking they sounded complicated.  You made it sound easy - and...

Related to the foreign key suggestion - do you have indexes on the foreign key columns in the other tables?  This will speed the lookup significantly.

What account are your SQL Server instances running under?  What about their respective SQL Server agents?  How did you configure your replication agent to connect to the database - SQL...

And I bet the mechanics of having the auto-inc number generated within a view would make it rather inefficient - i assume your other tables store the identity value and...

You are near the mark, but you will need to employ dynamic SQL.

So the part of your code that looks like
ALTER TABLE @name
ADD created_by [VARCHAR] (25)
GO
ALTER TABLE @name
ADD created_by [VARCHAR]...

Could it be that you do not have identity ranges set for each of your databases?  You should specify a range of identities per database to ensure that inserts from...

Hi.

The difference is that first of the "duplicate" locks on the key itself was an exclusive lock on the key (preventing others reading/writing at all under the normal isolation level)-...

The SQL Server Service on machine 'A' must run as a user account on machine 'A' - this would be administrator + no password.  BUT, it then cannot connect to...