This is just an example that might change the results even at each service pack level, you should use the recommended practice:

select * from mytable

select @err= @@error, @cnt = @@rowcount

if...

I believe one of the most anoying feaures is that it does not give you the ability to SCRIPT OUT the plan. It will be really portable and easier to...

I am with Remi on this one. SQL is what puts my food on the table, not access  

OK,

There is a problem here also in the data used to simulate this. If you use what you posted, the cardinality of the index will be so low that I...

>>Point 2:  I'm not sure what you mean.  Are you saying I need a larger table to see the performance return on EXISTS<<

ABSOLUTELY! if the number of rows is small...

1.First and foremost INDEXES DO MATTER!!!

2.Second, the number of rows must not be trivial

3.And Last but not least the HW in some cases...

I can give you one reason.

If the number searched (t2.v) exists more than once on t2 exists only will test for the first your join will have to work...

have a look at suser_sname() in BOL

HTH

NICE!

I'll keep this one in mind, thank you for sharing

Because my life has tought me not to trust one opinion (HW manufacturer) I would schedule a CHKDSK on the SAN Disk you had problems when the next maintenance window...

they use the guest account that is part of the public role and can not (should not ) be removed!

HTH

Allow me to differ.

As long as you have to go through a bandwith bottleneck (compared with IDE/SCSI bandwith) SQL Server will be SLOWER than many Desktop DBs !

I hope you are not comparing access on a local machine against sql server on a remote machine!

the RESEED only change the last / next  value not the increment therefore you have to follow Frank's suggestions

HTH

This remainds me about a consulting occasion in which I had to redesign the work performed in three years. It took me 4 months and not because I was good,...