Try running DBCC TRACESTATUS to check which trace flag is set on. After that you can turn it off DBCC traceoff command

Adi

Actually, if the target table already exists, you need to run an insert select statement. Something like this:

Insert into TargetTable (col1, col3)

Select colA, ColB

From target server

For more...

As far as I know the only way is to read about it in BOL. If it exists just for backward compatibility, BOL will state so.

Adi

The fact that you always got the same results at the past doesn’t guarantee that you’ll always get the same results at the future. If something would change in...

Just out of curiosity – Why would you want to change the name of all columns to be in upper case?

Adi

I have to admit that Carl's post did surprise me. I wasn't aware of problems with accuracy of money data type, and suddenly he came up with something that...

--creating test table

create table test (id int, string varchar(100))

go

--inserting demo data

insert into test (id, string)

select 1, 'aaa'

union

select 1, 'bbb'

union

select 2, 'ccc'

union

select 3, 'ddd';

--using for xml cluse with path...

t.hitendra (6/16/2009)

---

Hi Adi,

Thanks for correction I wasn't sure about clustered index on primary keys though.

May be you can point what anomalies could arise if...

Don't trust the information from sysdepends table. There are few cases that you will not see the dependency of objects. Beside the scenario that you showed there...

You can use an instead of trigger and change the value of the column according to the original value that the user used. I suggest that you'll read BOL...

t.hitendra (6/16/2009)

---

hi there,

I would love to know why do you need two primary keys in your table.

Although i think in relational database a primary...

This is taken from BOL:

" rowversion is the synonym for the timestamp data type and is subject to the behavior of data type synonyms. In DDL statements, use rowversion...

Grant Fritchey (6/15/2009)

---

I seriously doubt it'll be the US, but I always hold...

It is possible. Few reasons that can cause this:

1) Different data in each server can cause different query plan.

2) Different session settings (this one can also cause different query...

There could be many reasons for this behavior and it is impossible to find it without any details. Here are few things that I would check. First of...