not finding data does not sound like an "error" to me in this case, so raiserror is probably no what you really want.

i think you just want to send an...

Siberian Khatru (1/28/2015)

---

Pardon my ignorance (I'm still learning) but what is the "default...

it's the datatype.

by definition decimals or floats are represented by at least once digit left of it's...

the issue is scope: the use statmetn is valid only for the contents of the EXEC command.

ALL the statements have to be in the full exec command; once it finishes,...

you'd have to convert to varchar, are you sure that's what you want?

ACTLABCOST = case

...

isn't there an implied extra join(Cross join?) , because you aliased the table?

--because you aliased the table as p, isn't this an implied extra table gets auto joined?

UPDATE dbo.ProductsL1

SET...

Lynn Hendricks (1/27/2015)

---

I was looking for the same script, had a hard drive malfunction(with no backup) and lost my script library. so instead of reinventing the wheel.

anywho... I am getting...

first a redesign; there is no reason to put this in a trigger. if the trigger fails, your data disappears because the transaction gets rolled back.

the second issue is permissions:...

i guess i was expecting to see a different driver, and it should be the one that is specific to firebird, and not the microsoft driver:

darn i missed the link too!, here it is expanded out instead of aliased:

Phil Parkin (1/26/2015)

---

A brief search suggested...

you say you installed the firebird odbc, but the error message clearly says you are using MSDASQL and not LCBI.IBProvider.3, so offhand, i'd say you should script your linked server...

if the two servers are on the same network, you could use a linked server and 4 part naming conventions to pull the data; easily the fastest way, assuming the...

yes you can.

export the encryption key from your existing SSRS service, and then restore the encryption key on the new one.

backup both the ReportServer and ReportServerTempDb databases, and resotre then...

as long as you due your due diligence, and check to make sure you won't have any data conversion errors, you'd be ok;

here's a quick example: if you radaptation of...

remove the GO statements.

GO statments are not a SQL command, but instead something that SQL Server Management Studio uses to split batches.

also, i'd recommend bullet proofing your code like this...