Hi A.Faijurrahuman

Seems like you usin' your "Id" column in a wrong direction. Sequenced numbers without any gap should not be handled in a database but generated in client (when shown...

Hi

One way would be DISTINCT:

select DISTINCT t1.colB from #table1 t1

inner join #table2 t2 on t1.colA=t2.colA

Greets

Flo

Hi sridhar.yalamanchi

No interview questions, please.

Flo

Thanks, Jeff!

I intend to update the script to add some missing data types like HIERARCHYID, UDTs, GEOMETRY and GEOGRAPHY.

Wish you best!

Flo

PS: Sorry for being out of the forums since a...

Tested on 2008. Just tried on 2005 and get the same error as you...

For your error:

Strange, just deployed the function I posted on my server (as save assembly). Worked fine.

Your initial problem:

Probably it depends on the deterministic of your statement, as Matt said...

Hi

Never heard about this behavior. did you check for database locks?

Some tips for your split method:

Why do you use RegEx.Split? It's much slower than a direct string.Split.

Try to avoid the...

Hi Winston

I've got experiences in different other programming languages and technologies - because I'm a developer 😀

Back to your question:

If you are interested in some other technologies you can start...

Hi Brad

A really good book for SQL Server CLR is Pro SQL Server 2005 Assemblies but you need some general .NET (C#) or other OOP experiences since it is not...

Dang! Forgot that, sorry.

Glad we could help! 🙂

Hi Winston

You can use the HAVING clause and a SUM depending on your status:

SELECT

orderlineid

FROM #test

GROUP BY orderlineid

...

... nothing or raise an error within the trigger to show the caller that something was wrong.

Hi Michael

Seems you have to change your Request.Method from "GET" to "POST"

http://social.msdn.microsoft.com/Forums/en-US/vststest/thread/02dd800a-a9cf-4dca-bb55-16b5672e12ff[/url]

Greets

Flo

Unfortunately this option is missing. Trick is to set a break point into your CLR procedure and hit F10 (step over) in your test.sql.

Hi

Use SQLCMD variables instead of usual variables. This enables you to use one variable for the whole script (and can be used in SSMS).

Greets

Flo