I am not sure the error. It maybe cuased by characters that cann't be encoded by utf-8.

You can try to add encoding="utf-16" in the processing instruction section, i.e. <?xml version="1.0"...

I use SQL server extended property for tables and columns. You can define the properties in Enterprise manager or use exec sp_addextendedproperty manually.

I have a procedure to generate the TSQL...

Maybe I didn't make me clear. What I mean is that if the Nth column can have NULL value in the table, COUNT(*) and COUNT(N) may have different value.

In the...

If you just want to avoid the error, SET ARITHABORT OFF. The value for that column will be NULL if it's divided by 0.

It's upto what you are going to achieve. If the first column is NOT NULL, COUNT(*) and COUNT(1) have the same result. If it's NULLable, the result may be different.

USE...

From the original post, I am not very clear it's two tables or two databases.

Join two big tables usually cannot give you good performance. Use table variables, i.e. retrieve...

If you have OPENXML inside your transaction, you can potentially have memory leak.

1) XACT_ABORT set to ON. When PK or constarint error occurs, the statment is terminated immediately.

2) XACT_ABORT set to...

you can parse the xml into a table variable, then insert into the two different tables based on your criteria

Though auto grow by a fixed size is criticl to a big and busy database, I prefer to allocate Big Enough Space manually when the db is setup or during the...

The size in sysfiles are number of pages. One page in SQL 2000 is 8 KB. To get the size in MB:

SizeInMB=size*8.0/1024.0=size/128.0

I am not sure where the conversion takes place. But IMHO, the architecture may result in big problems in the future.

1) It's the client side locale instead of country that...

I encountered several times of suspect db. What I did were:

1) Made it online first of all.

A database can become suspect for several reasons. 

Try 

EXEC sp_resetstatus 'DB_Name'

first to...

You need to use CASE in your where clause. This sample works:

create table test (Num nvarchar(40))

GO

insert test values ('10')

insert test values ('20')

insert test values ('qa')

insert test values ('30')

insert test values ('b')

GO

select...

Not bad.

For OLAP, an alternative is to use RAID 5 for dw. For 6 spindles in RAID5, the read performance (reads from 5 spindles) will be better than RAID0+1 (reads...

Another reason maybe you do not have SET NOCOUNT ON in the your SP. This will return one more record set to your client.  It's not a problem for QA....