Nothing in the agent log, error log or job history? Is this a maintenance plan job or a custom procedure?

You can right click SQL Server Logs and go to configure.

But here is the command:

EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'NumErrorLogs', REG_DWORD, X

Where X is the amount of error logs kept before...

Wow, I really appreciate the information all.

So minus an export/import process and/or buying a driver/software, there is no way to opendatasource/linked server to a progress db from SSMS then eh?

Thanks guys, waited it out a bit, ran again, worked fine. Never seen that before.

Thanks

haha yeah, I swear ... I'm slow on Mondays ... never been a coffee drinker though :(...

Ah ok, I see what you're saying ... yeah that works too. For now I just used an alias on the source server, but I think I'll take your route.

Thanks

Another oddity found ... joining the job_id from [xp_sqlagent_enum_jobs] to msdb.dbo.sysjobs results in some not matching up ... can't figure out why yet. About 90% or so of my entire...

I only have one server in the environment that runs on a different port (don't ask why). Anyways, I tried servername:port# and that doesn't work ... only way I can...

Yeah, a local insert into exec without opendatasource would work perfect... how did I not think about that. Jeez ... Mondays. Thanks man.

Now I gotta resolve a An INSERT EXEC...

That VBScript not work for you?

Figured it out … I guess? Using the wizard, it doesn’t like temp tables, but as is in a dataset, it worked fine.

Thanks for the feedback MANU. Hopefully in the very near future this along with over 100 other very good DBA scripts/apps/utilities/etc. will be available online. I don't usually post my...

? It is a system stored procedure accessible from any database ... try xp_readerrorlog. You can also view the error logs through the management tree in SSMS or on the...

Well, be that as it may, the link does state that there is no upgrade support...

If you still can't find resolution, I'd say make a call to Microsoft.

I know what you're talking about and I have also tried to find a solution for this ... it's a PITA when you have a very large table and don't...