yeap its an association table between two tables.

[font="Courier New"]You can do it by two ways ..[/font]

[font="Courier New"]1. using "LEFT JOIN"[/font]

[font="Courier New"]SELECTT1.*, T2.*

FROMT1

LEFTJOIN T2 ON T1.keycol = T2.keycol

WHERET2.keycol IS NULL[/font]

[font="Courier New"]2. using "EXCEPT"[/font]

[font="Courier New"]SELECT keycol, col1, col2, col3,...

Whether to use replication in development enviornment or not?

nice article can you also give us the solutions to make it resistent

No. There are no security setttings in the package.

As i mentioned ealier this is true we have dirrenent service packs installed on both source and destination server. I am bemused how it is working earlier with same specifications....

the reason you are getting the deadlock is sql server executes both the statments as two different batch

it first executes the " begin tran exec sp_addtype 'Udd_dummy','int' part in...

any suggestions how can i reduce it.

We wish you and all a Merry Christmas 2009..:-)

You can refer to BOL / MSDN for rules/ in how you can use the order by clause.

I checked the profiler.

I assume that you have different job for Transaction log backup, if so then you can set the Notifications / Alerts on Job failed.

Nope I dn't have any trigger's on the tabl. The table structure is simple.

1. Primary Key

2. 7-8 Foreign Keys

There is another option that you can use to kill all active connection the database and make database read only

ALTER DATABASE <mydb> SET READ_ONLY WITH ROLLBACK IMMEDIATE

I was also facing the same issues even I tried all the solutions mentioned here & some other solution except stopping or pausing the server.

I used another trick for it.

1....