just checking the basics...the connection string your program is using is connecting to master database and not the database you are trying to restore right? if it connects to teh...

just checking the basics...the connection string your program is using is connecting to master database and not the database you are trying to restore right? if it connects to teh...

doh! that was it! thank you Gail, and thank you Barry for a handy snippet to add to my collection.

RBarryYoung (5/8/2009)

---

Looks like I answered my own question. The following seems to work fine:

Declare @qp as XML

SELECT @qp = query_plan

From sys.dm_exec_requests

Cross Apply sys.dm_exec_query_plan(plan_handle)

Where session_id =...

if the trigger does not exist, you can't ALTER it..change to CREATE TRIGGER.....

my WAG on the column name was perfect!

change that last line to this:

WHERE tblPerson.PersonID = INSERTED.PersonID

you pasted your current trigger...i modified it.

however, i made a WAG(Wild *** Guess) as to whether your table tblPerson had a PersonId in it.

you'd have to modify it to be...

you probably want to change it to test for OR instead of AND...so it builds like this

SELECT * from MyTable WHERE 1 = 2 --never happens

OR ServiceNumber001Volume...

your current trigger would update everything, where you really want to restrict it to the rows that were updated.

inside a trigger, there are two virtual tables called INSERTED and DELETLED,...

you'd have to use dynamic sql to build the sql; here's a working example:

Create Table MyTable(

Id int,

Name varchar,

Address varchar,

ServiceNumber001Volume int,

ServiceNumber002Volume int,

ServiceNumber003Volume int )

declare @sql ...

your welcome pav; settings like that are not always intuitive.

for others reading this, pav was referring to how to export from Query Analyzer with a custom pipe character; the thread...

the format has nothing to do with the server you are connecting to...it's a setting for Query Analyzer.

just change your export format here:

you could still add a default constraint later...but that's beside the point.

you are right, you might need to do something in a trigger that is not quite doable in a...

I think you are a bit confused on default and timestamps.

the "timestamp" datatype is poorly named, and should be referenced by it's synonym called rowversion is a special datatype...

i read his requirement as being that the Customer_Tags table was a many-to-many table with CustomerId , with FK's to other...