Well, now that you explained it, I'd suggest to abandon the special formula for last names with exactly 9 characters and make it always first 8 of last name plus whatever is...

IMHO the number of users does not affect solution regarding number of databases in any way. We have almost 200GB database with normally about 40, in peaks up to 80 concurrent...

I don't know about any way to do this automatically and immediately, based on insert into a table... but maybe it's just that I never needed it that quickly

You could try this one, though I'm not sure how efficient it is - you have to test it. It works on the assumption that you have some ID on...

I'll be glad to assist you with locking, but what precisely is the problem?

Generally, SQL Server decides for every query what type of locking is best - rows, pages or...

Another way to do it:

CREATE TABLE #yourtable(field1 varchar(100))

DECLARE @input_string varchar(200)

DECLARE @parse_string varchar(200)

SET @input_string = ' Eko Indriyawan  Lagi Makan '

/*strip leading and trailing spaces*/

SET @parse_string = LTRIM(RTRIM(@input_string))

/*if there are any...

Now that I see Gila's post, it seems that I have misunderstood the question. The SQL I posted only changes tan and beige to lightbrown in those cases, where both these colours...

I'd say split the action into 2 parts. First, find all names that have both tan and beige and update 'tan' to 'lightbrown' + 't' to 'lb' in them. Do...

Are you sure you are granting the privileges to the correct account? The one that she uses to log on? E.g. when switching from SQL authentication to Windows (domain) authentication, there can...

It would help us immensely if you could describe in words, what is the desired result. From your post and example it is impossible to know precisely, several different conditions could satisfy it.

For example, for...

RLSQL, I think that it would be best to decide whether you want to use the foreign key functionalities or not. Either drop the foreign key constraint altogether and leave...

Hmm... I don't know why you are using a cursor, if you don't want to loop... but anyway, there is no equivalent is SQLS 2000. If I remember correctly, ROWNUM...

You're welcome 🙂

just want to warn you - if I didn't overlook something, this ID will be reported as correct by the SQL you are using : '+00e5*00007d'.... not sure about...

I looked at it once again and found a workaround, more reliable than using ISNUMERIC. Corrected SQL that should do the task:

DECLARE @ID CHAR(12)

DECLARE @ID_pattern CHAR(12)

DECLARE @allowed VARCHAR(100)

DECLARE @transform VARCHAR(100)

DECLARE...

Let's try an entirely different solution... it looks a bit strange in the beginning, but it works fine. There should be no problems with collation, and it makes rather easy to...