Hello Mohammed,

these views "preserve information for instances ugraded from a previous version of Microsoft SQL Server" (from BOL).

select * from dbo.sysdbmaintplan_databases

Returns nothing (0 rows) and...

select * from dbo.sysdbmaintplans

Returns one row...

Hello Joshy,

Don't think there is something equivalent in SQL 2005 .

Carl.

Its as you said...

By the way I didn't have the time to schedule a public humiliation session, too much work to do fighting against sp_MSforeachdb... '+db_name()+'.sys.schemas WHERE name = '+''''@username+'''')

IF (@@ROWCOUNT = 1)

 ...

sp_MSforeachdb is really a "black box"......

In sp_MyWork using this call method:

SET @sql = 'EXEC ?.dbo.sp_MyWork ' + CONVERT(varchar(10), @a)

EXEC sp_MsForEachDB @sql

I cannot query data dictionnary (sys schema views). I...

It works well.

Thanks a lot Ninja.

Carl

Wow... Thank's a lot "Ninja" for this example .

I'll try it soon.

Best regards.

Carl

Can I pass a variable to sp_MyWork using EXEC sp_MSforeachdb 'EXEC ?.dbo.sp_MyWork' ?

I have to call sp_MyWork with a username...

How?

Regards.

Carl

I'll avoid to punish myself

Thanks.

Carl

Thank's... I will try it with the unofficial  stored procedure sp_MSforeachdb.

Best regards.

Carl

Hello John,

Can I do that with dynamically found databases?

Regards.

Carl

Hello John,

It could be the case..

But what I was thinking is:

(1) Create a stored procedure in the master database called sp_MyWork

(2) Run the stored procedure against "hardcoded" or "dynamically found"...

Hello Greg,

It is exactly the problem.

I also had to restart the Agent service.

Thanks a lot.

Carl

Forget it we found:

http://www.microsoft.com/technet/technetmag/issues/2006/01/ProtectMetaData/?topics=y

That explain this behavior.

Regards.

Carl

Hi Holger,

Your were right! Its taht bug.

Thanks a lot.

Carl