I don't think the purpose of this particular use of XML is to make it meaningful.  It is used as a method to transport data. 

For the purposes of this...

Keep in mind that changing the collation of a database changes the default collation for newly-created columns.  It does not change the collation of existing columns.

Actually I would check the build number before doing any of those steps.

Select @@Version

I think this problem happens with SP3 if the build 818 hotfix isn't applied.

"...The CASE does not work...."

Hi Michael,

What doesn't work is that the conditional expressions in T-SQL don't function like C# or VB,  or just about any other language.

They require an operator, and...

Hello,

What is the result from Select @@Version on the publisher, distributor, and subscribers?

jeff

I assume that this was working before you added the new column.  I also assume that nothing else has been done to use the new column.

So, I don't see that there...

Hi cd,

If you are using Access with linked tables, I think you have to delete and re-link a table (IN the Access database, not on the SQL server) after you make changes.

jeff

Hi cd.

No worries about the wrong forum AFAIK. It happens. I just wanted to make sure.

On to your other question.  The position of a column in a table should never matter, provided...

Hi cd,

I read your post, and since you mentioned that you were using EM, I forgot that you were posting in the 2K5 replication forum.

Are you on SQL 2000 or...

Hi, here are examples.  You would run this on the publisher database.  RM00101 is the name of a table.  No I did not pick the name....

Your best bet is to...

Hi Giorgio,

I have this kind of thing up and running using the OLEDB provider (IBMDADB2) with fix pack 10.  Unfortunately, I'm not in a location that allows me to see the...

I think that the reason you get no output is that the leading 0x00 is interpreted as an end-of-string marker. 

0x62 is ascii lower case b, and 0x01 is control-a, but...

Hi George.

The "storage" referred to in the error message has nothing to do with disk space.  It's about a particular type of reserved memory. Insufficient space is usually reported as error...

"....SQL Server Cache Hit Ratio is almost always above 99%....."

Adding additional RAM might get rid of the "almost" part.   I would look at the PLE (Page Life Expectancy) counter over...

It looks like a success message to me.  Did you check to see if the file in the "Log backed up" message exists and has a log backup in it?

A...