Try putting a return in the field manually, maybe it's the control that is not set to show line feeds.

It basically opens a cursor and selects all databases on the server.

Then the command is the tsql you want executed for each of the databases on the server.  The question...

Just to give you an idea, it's only the 3rd or 4th time I see something like this in 2 years here .  So...

Most likely by losing a few weeks searching for it .

Tried running it without top... Stopped the query after 10 minutes, no dice .

Not that I don't want to believe you.  But excluding CLR, how the heck are you gonna do that??

I'd like to so some working code if you could provide some...

Just for the records..

4860 rows in dbo.SysColums of 2000

11237 in sys.Syscolums of 2005

So the cross join might be overkill in 2005 unless you realllllllllllly need 126 270 169 rows in...

All I can offer is silent support. 

Good luck sir.

That what this is for :

Create a table like UsersHistory

DateHistory smalldatetime not null default (getDate())

Then the job fills a table with the data you want. Now if you...

Sorry, got no guess on that one... Maybe the registration failed or didn't complete somehow?!

We can't see any image you post unless you put it up on a webserver... I certainly can't see any.

It seems to me like you are trying to create an dll that is not registered...

But I'm just guessing.

They both work.... 

I'd use the dts option to schedule the job, then if needed I'd go edit the schedule with the agent (kess work that way).  You'll understand once...

For future refferences... wasn't there an object name refferenced in the error message... I'm sure it would have pointed directly to the trigger erroring out and it would have been...

Thanx for the feedback... I knew we couldn't be all crazy around here.  There's at least one of us who figured it out .