you cannot change the datatype, but can you change the size?

for example, a 8 letter password using AES requires 40 characters to store the hashed value...

so if you cannot change...

I think the original poster is out of luck.

when you script a linked server, you get this specific comment/message, telling you that it won't script the password:

/* For security reasons...

camiloaguilar1 (10/21/2010)

---

I got that clear but I did not explain it that good, I create that table in temporal way. The goods are already with the client to so modifications...

i updated my post with a second sql, probably while you were reading the first version of the post...so the second...

camiloaguilar1 (10/21/2010)

---

Because we have a lot of order details from a sale. So for no wasting of lot of order papers we want to make 1 order from all the...

on my db with 51 databases, this gives me 26 rows: what does...

make sure you are comparing the actual execution plans, and not the estimated plans....

the estimated woudl probably be teh same on both, but the performance issue is in the actual...where...

well you didn't provide any examples of what was going wrong;

here's the data you posted in a consumable format, as well as a query that pulls the data you were...

Please don't crosspost. It just wastes people's time and fragments replies.

No replies to this thread please. Direct replies to http://www.sqlservercentral.com/Forums/Topic1008657-391-1.aspx

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...