internal activation of service broker

Hi, there,

I'm a Chinese fan of Microsoft SQL Server 2005. Through studying for MS SQL Server 2005, now I have a question about ‘internal activation of service broker’.

At the moment I have done a test. The description of test is as following:

Firstly I set the status of the activation to be off (ALTER QUEUE [dbo].[TargetQueue] WITH STATUS = ON , RETENTION = OFF , ACTIVATION ( STATUS = OFF , PROCEDURE_NAME = [dbo].[Usp_HelloWorld] , MAX_QUEUE_READERS = 5 , EXECUTE AS N'dbo' )). And filled the queue with100000 Messages. Then that running another application caused the usage of the CPU achieve 100%. Secondly reset the status of the activation to be on and monitored the ‘sys.dm_broker_activated_tasks’. The instance of the stored procedure got the maximum number 5 very quickly. The server was much slower at current.

The SQL Server 2005 Books Online says: ’an activated stored procedure typically processes one or more messages and returns a response to the service that originated the message or messages. When messages arrive faster than the stored procedure processes messages, Service Broker starts another instance of the stored procedure, up to the maximum number defined by the queue.” But it doesn’t mention the performance counter of the server, for example: If the usage of the CPU is very high, the queue readers should be as few as possible, even don't process the message of queue until the system is idle. Because a client choice service broker means he don’t care immediately process message, contrarily he care the throughput of the system and don’t bother the natural application.

So my question is whether the strategy of internal activation of service broker doesn’t care the performance counter of the server, just care the speed of process message. And the priority of queue monitor in SQL Server‘s internal processes. Unfortunately I can’t find any information about these from books online and Internet.

When messages are available, an activated procedure will run at normal prioirty, no different than running a T-SQL batch from an user connection. You should not set the max_queue_readers higher than 2 times the number CPUs available to SQL Server, better 1 x number of CPUs.

If you need to reserve more CPU room for user activity, it means you need a bigger machine (more CPUs)

HTH,
~ Remus

|||

I want to know: why SQL Server can't activate more procedures when the the system is idle and activate lower procedures or no procedures when the sysstem is busy. I think it's a good way to improve throughput and very easy for sql server to do it.

|||

You can use the product feedback to make a suggestion for this: https://connect.microsoft.com/SQLServer/Feedback

Ususaly this is achieved in practice by changing the number of maximum activated procedures based on a operation schedule (e.g. add more procedures off hours, reduce at peak hours). An Agent job or event a SSB timer message can be used to run the ALTER statement that changes this number.

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
Thanks
Go through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thanks

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
ThanksGo through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thankssql

Interesting Behavior of Service Broker Queues

Hello All:

I've been experimenting with the new SQL Server Service Broker, and I think I've discovered some interesting behavior. Service Broker relies on "Queues" to store messages that need to be processed. Service Broker operates by sending a message from one Queue (the INITIATOR Quque) to another Queue (the TARGET Queue). A Queue can have an "Activation Stored Procedure" associated with it. This procedure is what actually processes the messages in the Queue.

The first behavior I obeserved related to the setting of a Queue's RETENTION parameter. The RETENTION parameter indicates whether or not the Queue will retain a copy of the messages it receives. By default, the parameter's value is "OFF" (meaning it will not retain messages). In the Activation Stored Procedure of my TARGET Queue, I used "sp_send_dbmail" to send an e-mail message. I wanted to capture the "conversation_handle" (a uniqueidentifier that identifies a particular message) and include it in the body of the e-mail. I was unable to capture it, because the Queue's RETENTION parameter was "OFF". When I tried to capture the conversation_handle from the INITIATOR queue (whose RETENTION parameter was "ON"), I was successful. The moral of the story is you apparently need to have RETENTION = "ON" if you need to capture information from a Queue.

The second behavior I observed relates to the setting of a Queue's MAX_QUEUE_READERS setting. This setting allows you to automatically invoke multiple instances of the Activation Stored Procedure. As messages come into the Queue, the Queue creates an additional instance of the Activation Stored Procedure up to the number you specified in the MAX_QUEUE_READERS setting. This allows parallel processing of messages in the Queue. There is also a programming technique called a "RECEIVE LOOP" which is used for processing messages. In the RECEIVE LOOP, you have a parameter called WAITFOR which tells the Queue whether it should stay on constant alert for new messages or whether it should time out after a specified number of seconds.

If you have the Queue wait indefinitely (by not specifying a TIMEOUT value in the WAITFOR statement) and you have invoked multiple copies of the Activation Stored Procedure, the procedure will remain in memory indefinitely. Therefore, if you make a change to the code of the Activation Stored Procedure, the change will NOT be reflected in the Activation Stored Procedure until you change the STATUS of the Queue. I had changed my procedure so that it would not send an e-mail, but the e-mails kept coming. The e-mails did not stop until I executed an ALTER QUEUE statement. I ran "ALTER QUEUE queue_name WITH STATUS = OFF;" and then I ran "ALTER QUEUE queue_name WITH STATUS = ON;" After that, the changes were reflected in the procedure.

Be aware of this behavior as you design your Queues.

"The moral of the story is you apparently need to have RETENTION = ON if you need to capture information from a Queue."

I wrong about this. The reason I wasn't capturing the information the first time around was because I didn't alter the queue to reset the STATUS. I have since been able to turn off RETENTION while having the ability to capture information from the queue.

|||

Ken, some necessary corrections:

- conversation_handle identifies conversations endpoints, not messages. Initiator and target have distinct conversation_handles. Conversation_id is identifies conversations and is shared by initiator and target. A message is unique by conversation_handle AND message sequence number.

- RETENTION has nothing to do with the capability to 'capture' conversation handles. To obtain the the conversation handle on the initiator side one must get it from the output of BEGIN DIALOG. To obtain the conversation handle on the target side one must put the conversation_handle into the RECEIVE projection list. RETENTION is totally unrelated to this, it is intended for helping application implement compensation logic on failed dialogs. RETENTION keeps a copy of sent and received messages for the duration of the conversation. These messages are visible for the SELECT statement, but not for the RECEIVE statement.

- any stored proc that has an infinite loop, once launched, will stay in memory until killed (explicitly or implicitly) or until server shutdown. This is not specific to activation, is general SQL Server behavior. The only difference is that when this happens by invocation from a user connection it is usually killed implicitly, by that connection being closed or by the batch being aborted. Turning the queue OFF will cause the infinite WAITFOR(RECEIVE...) in the procedure to error and thus exit the RECEIVE loop. One could just as easily KILL the procedure (lookup the SPID in sys.dm_broker_activated_tasks). Needless to say, activated procedures with infinite loops are a very bad practice. It leads to unnecessary consumtion of server resources (threads at the very least) when there are not messages to receive.

- altering the code of an stored proc does not affect the exisiting running instances of that stored proc. This behavior is general in SQL Server, not particular to activated stored procs. Only new invocations of the stored proc will detect the change.

I hope this clarifies some of the behavior you observed.
HTH,

~ Remus

|||

Thanks for the clarifications. I wasn't thinking of the RECEIVE LOOP as an infinite loop, since you don't see the timer on the Query Editor window keep running, but it obviously is one. I also wasn't clear about the circumstances under which a stored procedure stays in memory, so thanks for that information as well.

Now I want to show you a code sample to clarify what I am doing. Is this what you mean by "put the conversation_handle into the RECEIVE projection list"?

<code>

USE ServiceBrokerTest

GO

/*

DROP PROCEDURE usp_FTPService

*/

ALTER PROCEDURE usp_FTPService

AS

BEGIN

DECLARE @.conversationHandle UNIQUEIDENTIFIER

DECLARE @.messageBody NVARCHAR(MAX)

DECLARE @.messageTypeName SYSNAME

DECLARE @.eMailBody NVARCHAR(MAX)

WHILE (1 = 1)

BEGIN

BEGIN TRANSACTION

WAITFOR (

RECEIVE @.messageTypeName=message_type_name,

@.conversationHandle=conversation_handle,

@.messageBody=message_body

FROM [FTPQueue])

-- If a message was received, process it, else skip

IF (@.@.rowcount <= 0)

BREAK;

-- Process ObjectFTPStartRequest message

IF @.messageTypeName = N'ObjectFTPStartRequest'

BEGIN

SET @.eMailBody = 'FTP job for Object conversation ' + CAST(@.conversationHandle AS NVARCHAR(MAX)) + ' completed'

EXEC msdb.dbo.sp_send_dbmail @.profile_name = 'Ken',

@.recipients = 'username@.domain.com',

@.subject = 'FTP Service Response (ASP)',

@.body = @.eMailBody;

SEND ON CONVERSATION @.conversationHandle

MESSAGE TYPE [LookupRaceFTPStartResponse]

(N'<ObjectFTPStartResponse>

FTP job for Object completed

</ObjectFTPStartResponse>')

END CONVERSATION @.conversationHandle

END

COMMIT

END

COMMIT

END

</code>

If that's what you meant, then that's what I was doing. The reason I was having a problem was solely due to the fact that the first version of the procedure was still running in memory.

|||

To put the conversation_handle into the projection list it simply means to have the conversation_handle in the list of columns you RECEIVE. You are doing this fine.

The code you posted needs two changes:
- the WAITFOR(RECEIVE ...) must have a timeout. Typically, the value should be a few seconds. The ideea is that the procedure should linger a bit, in hope a new message arrives and it can be processed. Too short interval and the procedure is gonna miss new messages, exiting and being re-launched, which is a somewhat expensive operation. Too long and your procedure is going to consume server resources w/o doing anything.
- You must add a TOP(1) clause to the RECEIVE. Otherwise you will receive multiple messages, but only process the last one.

HTH,

~ Remus

|||

I don't think it's proper to say the TIMEOUT is required since the T-SQL language does not require a TIMEOUT with the WAITFOR clause. If it were required I would get a syntax or runtime error upon execution of the code.

As for whether it's a good idea to use a TIMEOUT, here's what Roger Wolter (Microsoft's Group Program Manager for SQL Server Service Broker) says in his book "The Rational Guide to SQL Server 2005 Service Broker" (Page 56):

"A WAITFOR with no timeout means the RECEIVE will wait for a message no matter how long it takes. Waiting for a message to appear on the queue is generally more efficient than polling the queue by using the RECEIVE command periodically. The main exception to this would be a low priority queue that is only polled for messages periodically when higher priority queues are empty."

As for the use of the TOP clause, I quote Roger again (again on Page 56):

"Retreiving all the messages available utilizes fewer server resources than multiple RECEIVE commands, so you should avoid the TOP clause whenever possible. The main reason to use the TOP clause is in stored procedures where receiving one message at a time into TSQL variables simplifies programming, or when there's a chance that a RECEIVE command will retrieve more messages than you want to process in a single transaction."

|||

Indeed, the TIMEOUT is not syntactically required. But no TIMEOUT in activated stored proc loop practicaly turns it into an infinite loop and you'll run into the problems you encountered.

Assignment in RECEIVE projection list (e.g. @.conversation_handle = conversation_hanlde) requires a TOP(1). It is true that using the TOP clause is less efficient, but otherwise the procedure gets significantly more complex. You'd have to RECEIVE INTO @.tableVariable, open a cursor over the table variable and scan this cursor. That is what the "simplifies programming" part of he's quote reffers to. You either use a simple T-SQL program (i.e. @.variables), but pay the penalty of the TOP clause, or you use a more complex T-SQL program (i.e. @.tablevariable and cursor). Roger himself mentions this, see the two examples of RECEIVE on page 57.
Note that if 99% of your RECEIVEs would return only one message anyway (as is often the case), then the TOP is not expensive at all.

See the Receive Loop example on page 63, you'll see that Roger uses both a TOP(1) clause and a 5s TIMEOUT.

HTH,
~ Remus

Integration with Sharepoint Server 2007 - Second instance of servi

Ok, I have a SQL 2005 sp2 server running reporting service on one server, and
Sharepoint Portal 2007 on another server. As I have reports setup and want
to continue using reports manager, I installed a second instance of Report
services on my SQL server. I installed Portal server on the SQL server (as
front end server) and it appears as a member of the Sharepoint farm. I setup
a new database using the Reporting services Config wizard in integrated mode.
I am using a domain user for the windows and web service accounts.
On the sql server when browsing to the virtual directory for the reports
server "http://servername/reportserver" I get the following error:
"The report server has encountered a configuration error. See the report
server log files for more information. (rsServerConfigurationError) Get
Online Help "
from other network locations, I get a request for authentication that always
fails.
The log file contains the following:
w3wp!webserver!1!6/11/2007-10:24:13:: i INFO: Reporting Web Server started
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing ConnectionType to
'0' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing IsSchedulingService
to 'True' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
IsNotificationService to 'True' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing IsEventService to
'True' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing PollingInterval to
'10' second(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
WindowsServiceUseFileShareStorage to 'False' as specified in Configuration
file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MemoryLimit to '60'
percent as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing RecycleTime to
'720' minute(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MaximumMemoryLimit
to '80' percent as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MaxQueueThreads to
'0' thread(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing IsWebServiceEnabled
to 'True' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MaxScheduleWait to
'5' second(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
ProcessRecycleOptions to '0' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration
file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing RunningRequestsAge
to '30' second(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing CleanupCycleMinutes
to '10' minute(s) as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
DailyCleanupMinuteOfDay to default value of '120' minutes since midnight
because it was not specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing WatsonFlags to
'1064' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
WatsonDumpOnExceptions to
'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'
as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
WatsonDumpExcludeIfContainsExceptions to
'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'
as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
SecureConnectionLevel to '0' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing DisplayErrorLink to
'True' as specified in Configuration file.
w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
w3wp!resourceutilities!1!6/11/2007-10:24:13:: i INFO: Reporting Services
starting SKU: Standard
w3wp!resourceutilities!1!6/11/2007-10:24:13:: i INFO: Evaluation copy: 0
days left
w3wp!resourceutilities!1!6/11/2007-10:24:13:: i INFO: Running on 1 physical
processors, 2 logical processors
w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Database Cleanup (Web
Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Running Requests Scavenger
timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Running Requests DB timer
enabled: Next Event: 60 seconds. Cycle: 60 seconds
w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Memory stats update timer
enabled: Next Event: 60 seconds. Cycle: 60 seconds
w3wp!library!1!06/11/2007-10:24:14:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the report
server log files for more information., SharePoint content service is null.
Report Server may not have joined the SharePoint farm, or Report Server
service account may not have been granted access to farm.;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the report
server log files for more information.
w3wp!library!7!6/11/2007-10:25:13:: i INFO: Catalog SQL Server Edition = Standard
I have read a large number of posts, and went through installation steps
repeatedly. I setup SPN for the webservice account. I just can't see what I
am missing.
Please advise.
--
Fredrick A. Zilz
Director IT
InterHealth N.I.I made one step forward. I found I had a duplicate SPN which was preventing
a log in to the Reportserver web site. So I can now browse to the
http://machinename/reportserver site. I am, however still not able to set
the default settings on the Sharepoint Portal side. I may need to move this
to a sharepoint group.
Thanks in advance for any advice.
--
Fredrick A. Zilz
Director IT
InterHealth N.I.
"Fred Zilz" wrote:
> Ok, I have a SQL 2005 sp2 server running reporting service on one server, and
> Sharepoint Portal 2007 on another server. As I have reports setup and want
> to continue using reports manager, I installed a second instance of Report
> services on my SQL server. I installed Portal server on the SQL server (as
> front end server) and it appears as a member of the Sharepoint farm. I setup
> a new database using the Reporting services Config wizard in integrated mode.
> I am using a domain user for the windows and web service accounts.
> On the sql server when browsing to the virtual directory for the reports
> server "http://servername/reportserver" I get the following error:
> "The report server has encountered a configuration error. See the report
> server log files for more information. (rsServerConfigurationError) Get
> Online Help "
> from other network locations, I get a request for authentication that always
> fails.
> The log file contains the following:
> w3wp!webserver!1!6/11/2007-10:24:13:: i INFO: Reporting Web Server started
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing ConnectionType to
> '0' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing IsSchedulingService
> to 'True' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> IsNotificationService to 'True' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing IsEventService to
> 'True' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing PollingInterval to
> '10' second(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> WindowsServiceUseFileShareStorage to 'False' as specified in Configuration
> file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MemoryLimit to '60'
> percent as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing RecycleTime to
> '720' minute(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MaximumMemoryLimit
> to '80' percent as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MaxQueueThreads to
> '0' thread(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing IsWebServiceEnabled
> to 'True' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing MaxScheduleWait to
> '5' second(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> ProcessRecycleOptions to '0' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration
> file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing RunningRequestsAge
> to '30' second(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing CleanupCycleMinutes
> to '10' minute(s) as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> DailyCleanupMinuteOfDay to default value of '120' minutes since midnight
> because it was not specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing WatsonFlags to
> '1064' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> WatsonDumpOnExceptions to
> 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'
> as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> WatsonDumpExcludeIfContainsExceptions to
> 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'
> as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> SecureConnectionLevel to '0' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing DisplayErrorLink to
> 'True' as specified in Configuration file.
> w3wp!library!1!6/11/2007-10:24:13:: i INFO: Initializing
> WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
> w3wp!resourceutilities!1!6/11/2007-10:24:13:: i INFO: Reporting Services
> starting SKU: Standard
> w3wp!resourceutilities!1!6/11/2007-10:24:13:: i INFO: Evaluation copy: 0
> days left
> w3wp!resourceutilities!1!6/11/2007-10:24:13:: i INFO: Running on 1 physical
> processors, 2 logical processors
> w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Database Cleanup (Web
> Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
> w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Running Requests Scavenger
> timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
> w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Running Requests DB timer
> enabled: Next Event: 60 seconds. Cycle: 60 seconds
> w3wp!runningjobs!1!6/11/2007-10:24:13:: i INFO: Memory stats update timer
> enabled: Next Event: 60 seconds. Cycle: 60 seconds
> w3wp!library!1!06/11/2007-10:24:14:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
> The report server has encountered a configuration error. See the report
> server log files for more information., SharePoint content service is null.
> Report Server may not have joined the SharePoint farm, or Report Server
> service account may not have been granted access to farm.;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
> The report server has encountered a configuration error. See the report
> server log files for more information.
> w3wp!library!7!6/11/2007-10:25:13:: i INFO: Catalog SQL Server Edition => Standard
>
> I have read a large number of posts, and went through installation steps
> repeatedly. I setup SPN for the webservice account. I just can't see what I
> am missing.
> Please advise.
>
> --
> Fredrick A. Zilz
> Director IT
> InterHealth N.I.

Integration Services won't install

I am installing Visual Studio 2005 Professional on Windows XP.

I have finished installing Visual Studio 2005 Professional along with Service Pack 1. Now I am installing the Developer version of SQL 2005 that comes with Visual Studio 2005 Professional .

During the installation of SQL Server 2005, I got the following error during
the integration services installation portion:

Failed to install and configure assemblies: c:\program files\microsoft sql
server\90\dts\tasks\microsoft.sqlserver.msmqtask.d ll in the COM+ catalog.
Error -2146233087

Error message: unknown error 0x80131501
Error description: You must have administrative credentials to perform this
task.

I'm logged into Windows as Administrator.

This machine did previously have VS 2005 Standard and SQL 2005 Standard loaded. The software was RTM software as provided by Microsoft at their launch event. I did uninstall both products before attempting the upgrade.

Any help would be much appreciated.

Hi,

Refer below links for workaround

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136467&SiteID=1

http://geekswithblogs.net/waterbaby/archive/2006/08/03/87048.aspx

HTH

Hemantgiri S. Goswami

|||

This is an issue when Microsoft.SqlServer.MSMQTask is left behind in COM+ catalog. You can workaround it by:

1. Open Administrative Tools\Component Services

2. Go to Component Services\Computers\My Computer\COM+ Applications

3. Delete Microsoft.SqlServer.MSMQTask

Integration Services Designer (Visual Studio) very very slow

Hi all

I have some performance issues when developing Integration Service Package ...

It is very very slow for example when I try to add new connection in
Connection Manages, it takes about 2 minutes just to open the property window.

On another pc in the same environment it works ok.
In the past I have doing a lot of SSIS Packages ... Is there any cache to empty ?

Thanks for any comments

Best regards
Frank Uray

Have you tried the 'work offline' option in SSIS menu. That option will prevent SSIS to validate connections in the package at design time. I am not sure if that is the source of your problem; bt you can try it.|||

Thank you for your answer,
but this does not help, it is still very slow ... :-(

Best regards
Frank Uray

|||Um, well... What are your machine specifications? CPU? RAM? etc...

What's the version number of SSIS?|||

Hi Phil

Here are the specifications:
- Dual Core AMD Opteron 2.20 GHz.
- 3.50 GB RAM
- 160 GB Disk
- HP xw9300 Workstation
- Windows XP SP2
- Visual Studio 8.0.50727.42 (RTM.050727-4200)

Hope you can find out something ...

Thanks and best regards
Frank Uray

|||

That's weird. I have half of that hardware and same VS version and run with no problem. Do you get the same behavior even when you create a new project/package? Check the task manager activity as well.

|||

Hi Rafael

Yes, I can create a new project and when I try to
add a new connection it takes 2 minutes to open
the first dialogbox ...
TaskManager is very quiet ...

Also when I run a package on my pc, it takes about
this 2 minutes to begin running the package.
When I run it on the server, the package finishes in 30 seconds.

Thanks and best regards
Frank Uray

|||This could also just be caused by network configurations when trying to do the connection discovery.|||

1.For integration service designer You should also install SQL 2005 SP1 and

the SQL2005 hotfix 2153.

2.another tip I found in the newsgroups was :

In internet explorer go to Tools-> options-> advanced

Uncheck the tickbox "check for publisher's certificate revocation"

(tnx to Nico Verheire)

3.When the designer is extremely slow in complex data flows, you have to break up the package in severaldataflows and use raw files to transfer data from one data flow to the other. See article <http://www.sqljunkies.com/WebLog/reckless/archive/2006/05/01/ssis_largedataflows.aspx>

I hope this can help.

Met vriendelijke groeten - Best Regards - Cordialement - Mit Freundlichen

Gruessen

Jan D'Hondt

Jade bvba

www.jadesoft.be

Integration Services Designer (Visual Studio) is very very slow

Hi all

I have some performance issues when developing Integration Service Package ...

It is very very slow for example when I try to add new connection in
Connection Manages, it takes about 2 minutes just to open the property window.

On another pc in the same environment (Domain etc.) it works ok.
In the past I have doing a lot of SSIS Packages ... Is there any cache to empty ?

Thanks for any comments

Best regards
Frank Uray

Do you have the SSIS service running? That can sometimes speed things up because it caches information about tasks and components.

Other than that - its more likely this can be attributed to hardware or network issues. I suppose it could be a million and one things.

-Jamie

Integration service Express/2005

I finally bit the bullet and uninstalled all of Sql Server 2005 and installed Sql Server 2005 Express both Advanced and the Toolkit. I can get in and see everything locally and my production Great Plains server just fine through Management console. The one thing I can't do is open an integration package to process our credit cards.

It's a pretty simple integration, but when I go to open it in SQL Server Business Intelligence Development Studio, the only thing it shows installed was Reporting services, not Integration services. When I try to open the project it gives me:

"The application for project 'c:\pcard...' is not installed. Make sure the application for the project type(.dtproj) is installed."

I had a problem earlier with the gui not coming up but was resolved when I applied SS2005 SVP 2. Some items wasn't on the same version. I re-applied svp 2 after I installed SS express and still got the above. If I try and 'add' Integration Services, either thru Express or just regular ss2005, it says it's already installed.

Do I have to modify the registry so that it comes up on Business Intelligence Dev Studio? I can't run the integration if I can't open the project.

Hi Pete,

SQL Express does not include SSIS and the version of BIDS that installs with the Express Toolkit does not support opening SSIS packages. You will need to install one of the paid Editions of SQL Server 2005 to get SSIS functonality.

Mike

|||

Hi Mike,

when you say Express Toolkit does not support opening SSIS packages, do you mean it does not support saving packages or the schedule package?

I want to know if there is any way I can save packages and do the scheduled jobs strictly without the licensed SQL Server.

thanks in advance.

Mike

|||

hi Mike,

as Mike already pointed out, the BIDS version provided for SQLExpress does not allow you to open SSIS package..

BTW, SQLExpress does not provide the SQL Server Agent as well, so you can not even "schedule" package execution, and no "runtime" for SSIS is available.. you could, eventually, use DTS, as a runtime for it is provided at http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

regards

|||

Thanks Andrea...

I am still wrestling with SQL servers and I was wondering if you could give me a definite answer...

I am using enterprise manager to connect to SQL 2005 Express for snapshot replication. I've created new publications, and then using EXPRESS I created a local subscription to the publication.

But I could see no changes in my database.. Do you know why this is happening?

I tried to start the distribution agent (multiple publications) but some reason it can't connect to subscribers.

is this because 2000 and express can't connect to each other? or am I doing something wrong?

thanks

|||

Hi ,

I understand that the BIDS version installed with SQL Express Toolkit does not allow to open the SSIS packages. Does that mean that we cannot even execute an SSIS package from SQL server Express.

Thanks.

Vigya

|||

Hi Vigay,

Right, you can not use any part of SSIS in SQL Express, it isn't there. You can't run packages or anything else.

Mike

Integration service Express/2005

I finally bit the bullet and uninstalled all of Sql Server 2005 and installed Sql Server 2005 Express both Advanced and the Toolkit. I can get in and see everything locally and my production Great Plains server just fine through Management console. The one thing I can't do is open an integration package to process our credit cards.

It's a pretty simple integration, but when I go to open it in SQL Server Business Intelligence Development Studio, the only thing it shows installed was Reporting services, not Integration services. When I try to open the project it gives me:

"The application for project 'c:\pcard...' is not installed. Make sure the application for the project type(.dtproj) is installed."

I had a problem earlier with the gui not coming up but was resolved when I applied SS2005 SVP 2. Some items wasn't on the same version. I re-applied svp 2 after I installed SS express and still got the above. If I try and 'add' Integration Services, either thru Express or just regular ss2005, it says it's already installed.

Do I have to modify the registry so that it comes up on Business Intelligence Dev Studio? I can't run the integration if I can't open the project.

Hi Pete,

SQL Express does not include SSIS and the version of BIDS that installs with the Express Toolkit does not support opening SSIS packages. You will need to install one of the paid Editions of SQL Server 2005 to get SSIS functonality.

Mike

|||

Hi Mike,

when you say Express Toolkit does not support opening SSIS packages, do you mean it does not support saving packages or the schedule package?

I want to know if there is any way I can save packages and do the scheduled jobs strictly without the licensed SQL Server.

thanks in advance.

Mike

|||

hi Mike,

as Mike already pointed out, the BIDS version provided for SQLExpress does not allow you to open SSIS package..

BTW, SQLExpress does not provide the SQL Server Agent as well, so you can not even "schedule" package execution, and no "runtime" for SSIS is available.. you could, eventually, use DTS, as a runtime for it is provided at http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

regards

|||

Thanks Andrea...

I am still wrestling with SQL servers and I was wondering if you could give me a definite answer...

I am using enterprise manager to connect to SQL 2005 Express for snapshot replication. I've created new publications, and then using EXPRESS I created a local subscription to the publication.

But I could see no changes in my database.. Do you know why this is happening?

I tried to start the distribution agent (multiple publications) but some reason it can't connect to subscribers.

is this because 2000 and express can't connect to each other? or am I doing something wrong?

thanks

|||

Hi ,

I understand that the BIDS version installed with SQL Express Toolkit does not allow to open the SSIS packages. Does that mean that we cannot even execute an SSIS package from SQL server Express.

Thanks.

Vigya

|||

Hi Vigay,

Right, you can not use any part of SSIS in SQL Express, it isn't there. You can't run packages or anything else.

Mike

Integration service Express/2005

I finally bit the bullet and uninstalled all of Sql Server 2005 and installed Sql Server 2005 Express both Advanced and the Toolkit. I can get in and see everything locally and my production Great Plains server just fine through Management console. The one thing I can't do is open an integration package to process our credit cards.

It's a pretty simple integration, but when I go to open it in SQL Server Business Intelligence Development Studio, the only thing it shows installed was Reporting services, not Integration services. When I try to open the project it gives me:

"The application for project 'c:\pcard...' is not installed. Make sure the application for the project type(.dtproj) is installed."

I had a problem earlier with the gui not coming up but was resolved when I applied SS2005 SVP 2. Some items wasn't on the same version. I re-applied svp 2 after I installed SS express and still got the above. If I try and 'add' Integration Services, either thru Express or just regular ss2005, it says it's already installed.

Do I have to modify the registry so that it comes up on Business Intelligence Dev Studio? I can't run the integration if I can't open the project.

Hi Pete,

SQL Express does not include SSIS and the version of BIDS that installs with the Express Toolkit does not support opening SSIS packages. You will need to install one of the paid Editions of SQL Server 2005 to get SSIS functonality.

Mike

|||

Hi Mike,

when you say Express Toolkit does not support opening SSIS packages, do you mean it does not support saving packages or the schedule package?

I want to know if there is any way I can save packages and do the scheduled jobs strictly without the licensed SQL Server.

thanks in advance.

Mike

|||

hi Mike,

as Mike already pointed out, the BIDS version provided for SQLExpress does not allow you to open SSIS package..

BTW, SQLExpress does not provide the SQL Server Agent as well, so you can not even "schedule" package execution, and no "runtime" for SSIS is available.. you could, eventually, use DTS, as a runtime for it is provided at http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

regards

|||

Thanks Andrea...

I am still wrestling with SQL servers and I was wondering if you could give me a definite answer...

I am using enterprise manager to connect to SQL 2005 Express for snapshot replication. I've created new publications, and then using EXPRESS I created a local subscription to the publication.

But I could see no changes in my database.. Do you know why this is happening?

I tried to start the distribution agent (multiple publications) but some reason it can't connect to subscribers.

is this because 2000 and express can't connect to each other? or am I doing something wrong?

thanks

|||

Hi ,

I understand that the BIDS version installed with SQL Express Toolkit does not allow to open the SSIS packages. Does that mean that we cannot even execute an SSIS package from SQL server Express.

Thanks.

Vigya

|||

Hi Vigay,

Right, you can not use any part of SSIS in SQL Express, it isn't there. You can't run packages or anything else.

Mike

Integration service Express/2005

I finally bit the bullet and uninstalled all of Sql Server 2005 and installed Sql Server 2005 Express both Advanced and the Toolkit. I can get in and see everything locally and my production Great Plains server just fine through Management console. The one thing I can't do is open an integration package to process our credit cards.

It's a pretty simple integration, but when I go to open it in SQL Server Business Intelligence Development Studio, the only thing it shows installed was Reporting services, not Integration services. When I try to open the project it gives me:

"The application for project 'c:\pcard...' is not installed. Make sure the application for the project type(.dtproj) is installed."

I had a problem earlier with the gui not coming up but was resolved when I applied SS2005 SVP 2. Some items wasn't on the same version. I re-applied svp 2 after I installed SS express and still got the above. If I try and 'add' Integration Services, either thru Express or just regular ss2005, it says it's already installed.

Do I have to modify the registry so that it comes up on Business Intelligence Dev Studio? I can't run the integration if I can't open the project.

Hi Pete,

SQL Express does not include SSIS and the version of BIDS that installs with the Express Toolkit does not support opening SSIS packages. You will need to install one of the paid Editions of SQL Server 2005 to get SSIS functonality.

Mike

|||

Hi Mike,

when you say Express Toolkit does not support opening SSIS packages, do you mean it does not support saving packages or the schedule package?

I want to know if there is any way I can save packages and do the scheduled jobs strictly without the licensed SQL Server.

thanks in advance.

Mike

|||

hi Mike,

as Mike already pointed out, the BIDS version provided for SQLExpress does not allow you to open SSIS package..

BTW, SQLExpress does not provide the SQL Server Agent as well, so you can not even "schedule" package execution, and no "runtime" for SSIS is available.. you could, eventually, use DTS, as a runtime for it is provided at http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

regards

|||

Thanks Andrea...

I am still wrestling with SQL servers and I was wondering if you could give me a definite answer...

I am using enterprise manager to connect to SQL 2005 Express for snapshot replication. I've created new publications, and then using EXPRESS I created a local subscription to the publication.

But I could see no changes in my database.. Do you know why this is happening?

I tried to start the distribution agent (multiple publications) but some reason it can't connect to subscribers.

is this because 2000 and express can't connect to each other? or am I doing something wrong?

thanks

|||

Hi ,

I understand that the BIDS version installed with SQL Express Toolkit does not allow to open the SSIS packages. Does that mean that we cannot even execute an SSIS package from SQL server Express.

Thanks.

Vigya

|||

Hi Vigay,

Right, you can not use any part of SSIS in SQL Express, it isn't there. You can't run packages or anything else.

Mike

Integration service Express/2005

I finally bit the bullet and uninstalled all of Sql Server 2005 and installed Sql Server 2005 Express both Advanced and the Toolkit. I can get in and see everything locally and my production Great Plains server just fine through Management console. The one thing I can't do is open an integration package to process our credit cards.

It's a pretty simple integration, but when I go to open it in SQL Server Business Intelligence Development Studio, the only thing it shows installed was Reporting services, not Integration services. When I try to open the project it gives me:

"The application for project 'c:\pcard...' is not installed. Make sure the application for the project type(.dtproj) is installed."

I had a problem earlier with the gui not coming up but was resolved when I applied SS2005 SVP 2. Some items wasn't on the same version. I re-applied svp 2 after I installed SS express and still got the above. If I try and 'add' Integration Services, either thru Express or just regular ss2005, it says it's already installed.

Do I have to modify the registry so that it comes up on Business Intelligence Dev Studio? I can't run the integration if I can't open the project.

Hi Pete,

SQL Express does not include SSIS and the version of BIDS that installs with the Express Toolkit does not support opening SSIS packages. You will need to install one of the paid Editions of SQL Server 2005 to get SSIS functonality.

Mike

|||

Hi Mike,

when you say Express Toolkit does not support opening SSIS packages, do you mean it does not support saving packages or the schedule package?

I want to know if there is any way I can save packages and do the scheduled jobs strictly without the licensed SQL Server.

thanks in advance.

Mike

|||

hi Mike,

as Mike already pointed out, the BIDS version provided for SQLExpress does not allow you to open SSIS package..

BTW, SQLExpress does not provide the SQL Server Agent as well, so you can not even "schedule" package execution, and no "runtime" for SSIS is available.. you could, eventually, use DTS, as a runtime for it is provided at http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

regards

|||

Thanks Andrea...

I am still wrestling with SQL servers and I was wondering if you could give me a definite answer...

I am using enterprise manager to connect to SQL 2005 Express for snapshot replication. I've created new publications, and then using EXPRESS I created a local subscription to the publication.

But I could see no changes in my database.. Do you know why this is happening?

I tried to start the distribution agent (multiple publications) but some reason it can't connect to subscribers.

is this because 2000 and express can't connect to each other? or am I doing something wrong?

thanks

|||

Hi ,

I understand that the BIDS version installed with SQL Express Toolkit does not allow to open the SSIS packages. Does that mean that we cannot even execute an SSIS package from SQL server Express.

Thanks.

Vigya

|||

Hi Vigay,

Right, you can not use any part of SSIS in SQL Express, it isn't there. You can't run packages or anything else.

Mike

Integration of Analysis service to sharepoint

Is there any sites or demo on how to use sharepoint with the analysis services in sql server 2005. Does the reports generated requires RS as well?

Thanks,

Regards

Alu

There is an effort underway to make AdventureWorks dashboard demo available publicly but I don't know the details yet. Most likely it will coincide with the SharePoint 2007 release.

You should be able to plug-in any URL-addressable report in SPS. Of course, RS reports will work best :-) More details in the forthcoming CTP 2 of SQL Server SP2.

Integrating SQL Server 2005 with SP1

I have the SQL Server 2005 Developer DVD and i download the SP1

how can i integrate the Service Pack with the DVD content (Of cource after extracting on my HD) ?

This comes up from time to time and the best response I've seen so far is from Euan's blog. The short answer is no, it is not supported on the Developer SKU (only with the Express SKUs)

http://blogs.msdn.com/euanga/archive/2006/04/27/584637.aspx

Thanks,
Sam Lester (MSFT)