Jeff, Thank you so much for the help. I will correct the code

Jeff,

Sorry for the late reply,

continuation of the above topic...

As you asked, the below is one of the update statements we are using in stored procedure

Update de_norm_buscard_attr

...

Thanks John Mitchell for the explanation

I too agree with patrick, When we are compressing already compressed db we wont get much space in it. That is why i feel option C is correct

thanks

Please suggest me a way to avoid clustered index scan when only primary key is defined.

sorry, about the subject heading

it is "non clustered index on primary key column"

mikael,

Learnt something new today, thanks

I tried with the below solution to get the value from item code

DECLARE @XML as xml='

<root>

<item>1987</item>

<item>1654</item>

<item>1321</item>

</root>'; ...

I thought answer B is including answer A also, that is why i did not check answer A.

and i did a big mistake by not reading "select 2"

learned a lot...

magoo,

small correction to my previous post,

This is a good solution. In the query output, base_id is getting eliminated,but I need to get the the base_id record also

regards

hi magoo,

This is really a good solution, base_id is getting eliminated.

Thanks

thanks prasad, i tried with parameterized view but again my value is dynamic, so still trying to get some solution 🙂

sean,

The requirement is for hierarchy records. (child and parent records, for that I am passing the child id as parameter). I could create table valued function for the same requirement,...

Hi

I tried the query like the below

DECLARE @idoc int, @doc varchar(1000);

SET @doc ='

<ROOT>

<AA wpid="4" WPName="??92" sum="0" result="03:30 , 18" count="1">

</AA>

</ROOT>';

--Create an internal representation of the XML...

Hi,

1.Please verify replication Monitor to know the errors

2.when ever you are setting up replication, 1. you will create publisher. after this, pls verify the snapshot agent status and logreader agent...

Hi ,

This kind of error generally occurs when we are trying to drop the table which is already selected in article selection during the replication/ publication setup.

Does your changes reflect...