As said before, you don't need to guess the last digit of the second number as it can be only 3!

Saves one cross-apply...

Also, you don't need to check if the same digits from different joins are not equal (eg. if checked a.num<>b.num in one "join" you don't need to check it again...

You don't really need last join as the last digit of the second number can only be '3'

with a(num) as

(select 1 union select 2 union select 4 union select...

The man was in a wrong school :hehe:

There are...

Welcome to the forum!

In order to help you we will need a bit more details from you.

Please spend some time to read the following:

http://www.sqlservercentral.com/articles/Best+Practices/61537/

Looks like homework to me...

What have you tried so far?

It's hard to see what will "prove it beyond all doubt" for Sergiy....

List of assemblies can be found in SSMS under [Database]/Programmability/Assemblies. You can right-click and generate CREATE script or else.

Also, you can "select * from sys.assemblies" to see all registered assemblies...

I'm only joking, really. The "winner" here is not paid much... (I would say no paid at all :-))

I wonder which query...

Luis Cazares (9/11/2012)

---

Eugene Elutin (9/11/2012)

---

It does, after...

It does, after he fixed it to...

Brandie Tarvin (9/11/2012)

---

Forgive me a moment, Eugene, while I poo-poo your...

The best and easiest would be creating CLR function which will remove all non-digits from string using RegEx.Replace.

Also, you can create UDF in T-SQL (you will use PATINDEX and REPLACE...

CELKO (9/11/2012)

---

This design flaw is called attribute splitting. Would you have “Male_Personnel” and...

Luis Cazares (9/11/2012)

---

What about?

SELECT f1, COUNT( Q6_BRANCH) AS CountOfQ6_BRANCH

FROM (

SELECT format(WEEK_DATE, "YYYYMM") as f1,

TBL_AML_ERRORS.Q6_BRANCH

...