Option 1 would certainly be simpler.

Happy to help.

Here is an example of the computed column (incase you need it)

USE tempdb

GO

CREATE TABLE TableA

(

ColumnA VARCHAR(5),

ColumnB VARCHAR(5),

ColumnC AS ((ColumnA+'-')+ColumnB)

)

INSERT INTO TableA

(ColumnA,ColumnB)

VALUES

('Hello','World')

SELECT ColumnA,

ColumnB,

ColumnC

FROM TableA

DROP TABLE TableA

Hi,

I think you have two options here,

1. If the table is truly static (never going to change) then you could just run an update on the table to set column...

Happy to help.

I've created 2 functions, one thats using a loop to break up a string and then one using XML (thanks for the article - very useful).

On small data...

Can ignore that now, manged to resolve it using;

i.item.value('(*[local-name()=sql:variable("@searchelement")])[1]','nvarchar(15)')

Thanks.

Just one quick question,

I've created a function for which I can pass in XML and then the element name that I wish to extract, this should allow me to us...

Hi all,

Many thanks for the responses, certainly somethings to think about and try out.

Looking at the sample code, I think I am right in saying basically if the select finds a record then you want to return success and if it doesnt then...

Hi Vani,

Have a look at this;

http://blogs.msdn.com/sqlreleaseservices/archive/2008/02/15/end-of-mainstream-support-for-sql-server-2005-sp1-and-sql-server-2000-sp4.aspx

Moving the transaction outside of the loop will result in the appropriate locks being held for the duration of the loop.

The trick is (in my opinion) to have the transaction...

Hi,

Are you experiencing a specific error or issue with the code?

No problem, happy to help.

I couldnt be 100% on whether there will be issues, it really depends if your using features updated in the hotfix.

If it were me, assuming you cant remove the updates...

Hi Harsha,

The differences will be down to cumilitve updates, .2039 is SP4.

As for .2055, the link http://support.microsoft.com/kb/959420 may be of assistance. If you want to sync up the version...

Thanks for the reply nilmov,

I'm currently looking into the KB 937343, hopefully this will should resolve the issues.

Thanks again.