yes.

each ALTER TABLE statement must be executed seperately, but you can generate all the statements based on the metadata, so it depends what you want to do.

an example might be...

i don't have a true SQL 2000 installation, and the code works flawlessly in SQL 80 compatibility mode.

try doing a find and replace for INSERT INTO #Results --> INSERT INTO...

you need to test for the space before ave as well to avoid substrings of a street name:

you are already testing for a space after the {Ave} or {Ave.},...

Andreas your trigger is currently designed to handle only one row being inserted at a time...

if you are bulk inserting, only one row would be affected when you trip the...

security is getting tighter and tighter with each iteration of SQL;

it used to be that the Builtin\Administrators group was automatically added as sysadmins when you installed SQL.

That is no...

BULK INSERT behaves differently for triggers, but not sp_executesql;

it might be the way your trigger is written...lets look at the trigger itself and see if there might be a clue...

i believe the error is related to the fact that you have TWO left outer joins, but only one [ON]

you meant to left join S2 to S1, and then S3...

it's not possible.

if they login with a SQL logon, their windows information is not available.

other variables, like hostname, can let you know their machine name, but if it wasn't used...

i may have skimmed over your post too quickly and missed something, but it looks like you can get rid of all the variables, and simply fix the trigger to...

I opened my SQLStudio.bin file with a text editor, and it's a mix of readable strings and binary stuff;

when i looked into this before, every recommendation was to simply delete...

that threw me off too, as i expected it to be in a registry setting, but it's actually in a binary file.

it's an all or nothing thing, as far as...

i see two solutions here...raise an error or put the old value for the BI column back, and allow the transaction to go through.

something like this would simply put the...

no, you can't; the OUTPUT variable has access to the INSERTED and DELETED tables only;

so you need to pass in your original Id for example, so it could be part...

since SQL 2000 is limited to varchar(8000), and you may...

yeah i think you'll want to insert the output into a table variable, then join it to the original table to get everything you need:

DECLARE @myTableVariable TABLE(NewBrand_ID int,BrandName varchar(30) )

INSERT...