PATH('') instructs the XML generator not to generate a parent node for each row in the result.

This is explained in this article: http://www.sqlserverandxml.com/2008/08/for-xml-path-how-to-remove-node-from.html

HI,

This forum does not allow to post code with XML tags. Hence I replaced XML tags with "{}" and added a note to you, to replace them with XML tags...

The problem seems to be a copy paste error, and since XML tags are not displayed in the post, it is bit hard to debug. The same example is posted...

see if this works:

UPDATE c SET

[Longitude] = a.[Longitude]

,[Latitude] = a.[Latitude]

FROM [ClientAdmin].[dbo].[ClientTbl_DimStores] c

INNER JOIN [KBAdminTemp].[dbo].[mstStores].[Latitude] a

ON c.[StoreId]=a.[StoreCode]

FOR XML clause generates the output in XML format and the format of the output can be controlled using AUTO, RAW, PATH and EXPLICIT.

by me, it returns the first employee record.

are you running it from SSMS or from application?

You can use OPENQUERY() to execute it on the linked server. for example:

SELECT Version FROM OPENQUERY ( myserver, 'SELECT @@version AS Version' )

run "SELECT @@VERSION" on the server and it will show you which version it is running.

If you want to retrieve additional information, you can query using SERVERPROPERTY. for example:

SELECT...

Also note that both table names have spelling mistakes in your sample code. You need to correct them before running the code.

Hi santosh,

I see that the editor removed XML tags from my post and that is why you dont get the correct results. The cast should be as follows:

I am replacing...

Did you try the code I posted? It can process more codes.

You can look at "create_date" and "modify_date" from sys.triggers

SELECT * FROM sys.triggers

Agreed with Garadin that you might reconsider the design of the table.

here is one option using XML that produce the desired result and can handle even more error codes...

It looks to me that an index on registrationno will improve the performance of your SELECT queries, unless you have a large number of records having the same value in...

What do you get when you run "select * from sys.database_principals"