Nice hint looking into utilizing Profiler to get the understanding on how a script is getting composed by SMS

Thanks

Thank You for the Information

Thanks for the link

The info provided refers to SQL Server 2000

Have their be changes made to SQL Server 2005 regarding Multiserver Administration?

Thanks for the helpful link

I just wonder how the information from WMI can be received without running a script but rather using wbemtest

I ran the CREATE PROC statement including just a fraction of the OPENQUERY statement and was able to receive more detailed error message

Error Message:

Msg 7357, Level 16, State 2,...

It follows the proc 🙂

USE [MSA_AE]

GO

/****** Object: StoredProcedure [dbo].[usp_bbbb_aaaa_xxxx] Script Date: 09/17/2009 18:26:07 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

CREATE PROCEDURE [dbo].[usp_aaaa_bbbb_xxxx] AS

SELECT * INTO #A FROM OPENQUERY(linkedServer,...

Thanks for the Script

Will analyze => understand => and conquer 🙂

Thank you ,

That was perfect knowledge transfer 🙂

Mike

The strange part of all is that no checkpoint is getting specified during the package designing stage

After the package has been deployed onto the server the following user stored procedure...

OK,

Now I have learned why posting the same question in different groups is not recommended

Just causes confusion ...

And of course, who can read has an advantage.

Thanks Phil

Thanks

sp_helptext xp_dirtree --> xpstar90.dll

Thank you for this very interesting knowledge sharing

Just one more question: Do you guys actually know the names of the DLLs where the extended procedures "reside" in?

Greetings,

Mike

Hi Vishal,

Thank you for your contribution.

It was very interesting to learn where in the registry the network settings can be found

Since xp_regread is not referenced in SQL Server Online Books,...

Hi Phil,

How can I get to the post you recommend reading?

Thanks,

Mike

Hi Satish,

The strange part of all is that no checkpoint is getting specified during the package designing stage

After the package has been deployed onto the server the following user stored...