Happy to help. I didn't "see it" necessarily though, I tested it with the following:

declare @fullname Nvarchar(255)

set @fullname = ' abc def '

declare @FirstName nVarChar(255), @LastName nVarChar(255)

declare @space...

The firstname has a trailing space that could be eliminated with the following:

set @FirstName=SubString(@LastName, 1, @index - 1)

Regards,

Toby

I agree with the stored procedure, but I am not sure why you have to bother with placing the call in an SSIS package. You can just call it from...

The definition of the object is stored to disk. However, the "english definition" has little to do with the compiled plan that the query optimizer submits upon execution.

Regards,

Toby

I thought this was a no brainer until I saw that 37% got it wrong. It always use to bug me when one of my previous team leaders would talk...

The ORDER BY makes no difference. I run the following code and get the same error as will be shown. The only way your insert is going to work is...

Then just use active directory groups and grant permissions to the groups on the SQL Instance.

Use connection pooling from the IIS app pool. IIS will connect to the database with one account. You are not going to create an account for everyone on the internet....

The most important thing about the "best practice" is that you use Active Directory accounts. In other words DON'T use SQL Server account. From there the next best practice is...

You can use the following, let me know if you want a cursor or while statement to execute it programatically. Otherwise you can just execute the output:

USE MASTER

DECLARE

I get the same error in SQL 2000 as I expected. Is it possible that you are assuming incorrectly that the procedure ran successfully in SQL Server 2000? I am...

Update t1

SET t1.Parentrefrecid = t2.recid

FROM Table1 t1

Join Table2 t2 on t1.bookingid = t2.bookingid

WHERE t1.bookingid = inserted.bookingid

AND t2.dataareaid = '200'

Do you want to drop all the SQL logins that have a certain password? Can you restate what the criteria is for dropping the logins please.

CREATE LOGIN [DomainName\User Name] FROM WINDOWS with DEFAULT_DATABASE=[AccountingDatabase]

What Login did you map the user to? Another thing you can try is

USE AccountingDatabase

GRANT CONNECT TO [DomainName\User Name]

Regards,

Toby

Good question. I ran up against an issue in data before where it was not actaully a valid numeric value, but passed the isnumeric test and broke the process upon...