well now you have the desired contents for the email; now it's just a cursor based on that query:

here's part two of the example, where you send individualized emails:

DECLARE

...

it's been a while since i sued it but PSEXEC from the PSTools suite is designed for executing things on a remote system...there might be some permissions issues...

this thread has a really nice powershell script Gene Hunter posted for the community:

it scripts everything.

http://www.sqlservercentral.com/Forums/Topic1240480-1351-1.aspx

i was modifying an example named "notes" to match your data, but without the actual tables, I could not test it for valid objects.

if you can fix the syntax...

this one is tough, because i don't have the tables to test agaisnt.

this MIGHT return the email/string you want to send.

if it does, then this query is what you would...

your image is blocked at my work, some filesharing violation according to our IT guys......can you paste the code you are referencing instead of an image?

you are definitely going to have to help us help you here.

what xml?

are you reading a value from the xml,...

the part of your script here:

DEFAULT 1

Alter Table Demo ADD col1 Int NOT NULL DEFAULT 1

creates a default constraint ont eh column...so you can't drop teh column until you drop...

maybe, with openrowset, and assuming there is connectivity between the two SQL servers:

here's a couple basic examples:

SELECT *

FROM OPENROWSET('SQLOLEDB','Server=yourservernamehere;Trusted_Connection=Yes;Database=Master',

...

depends completely on what you want to monitor.

Monitoring usually refers to the whole server in general .

For built in reports, go to the Object Explorer in SQL Server Management...

if you think about it at a little higher level, the question is :

how can [something] make two connections and transfer data.

just as you are seeing, the possibilities boil down...

access denied is usually because the account the SQL service is running from doesn't have access to teh specific folder the mdf exists in;

for example, if the mdf is on...

if you change form inner join to left outer joins, won't you get the desired results, where the string is in one or more tables??

thbe error is here: you are mixing the old comma delimited join style up with the newer explicit join;

you should stick with the newer version, since it makes it clearer...

that's what we keep...