Activation

I was testing around with a sample service broker app using activation, and came across an interesting question. The little app sends a series of four messages to a queue, either on the same conversation or on seperate ones. Each message invokes one stored procedure in my activation procedure. All the procedure does is enter a record into a test table and then wait for an allotted amount of time. In my example, the first message called a proc that waited 20 sec, the 2nd one that waited 10 seconds, the third 5 seconds, and the 4th 1 second. I am using internal activation on the queue. It seemed that in both scenarios (sending on 4 separate conversations and on one conversation) the procedures executed "almost" sequentially. "Almost" meaning that the first procedure was done before the last one started executing. It makes sense to me that this would happen where I sent them on the same conversation, but not really when I sent them on 4 seperate ones. Is it because when I call a procedure from my activation procedure it locks the queue so that another message cannot be processed (I'm processing a message at a time)? How could I make it so that the 4th procedure (the one that only waits 1 second) returns before the 1st procedure (the one that waits 20 seconds)?MAX_QUEUE_READERS = ?|||

Sorry, my max_queue_readers where 5 in both situations.

Tim

|||

With one message per conversation then new instances of the stored procedure may be launched, so a message that arrived later may be processed sooner by a new instance activated procedure.

Also, even locally, the message order is only guaranteed within a conversation, so 5 messages sent on 5 conversation may arrive on the target queue in any order (unlikely to arive in different order, but one should not assume order between conversations)

|||You reference that new instances of a sproc may be launched for one message per convo, but what determines if it will or not? Will it only happen if some threshold is exceeded on the queue? The reason I was doing the little test was because I haven't seen any articles out there really detailing good ways to run large processing queries asynchronously for one application, so I was wanting to write one. My main curiosity was if there was any way to modify any of the settings for the procedure activation (which I don't think that there is).|||I just read your blog entry on Parallel Activation...neat stuff. Although, I doubt that it is something I would ever need to implement. I changed my procedures a bit so that they delay for a longer time period, and it appears that a new activation occurs ~ 5 seconds.

Accessing Reports/Databases across 2 domains

I have architecture related question -
I have 2 databases on 2 domains and security doesn't permit me to co-mingle
the data. I'll be generating 2 different reports for same request.
Question is - Do I need SQL server with reporting services installed on
each domain?
Current proposed solution is -
Domain AAA will have SQL server with RSS
Domain BBB will have SQL server with RSS
Sharepoint web parts (on BBB side) will access report from AAA and BBB.
(Domain BBB has 1 port open to allow web traffic).
If trusted SQL server connection is made available to RSS on BBB side, then
I think we don't need server with RSS on domain AAA. is this right? If so,
How can I access databases from RSS across domains?
Sounds interesing right? Please help me ....Sonali,
RSS is only needed to host the report definition which in turn collects
the data required. Provided the data connections are set up with
appropriate logins to the databases on each domain from the RS server,
you should be able to run from one RS server.
Your issue will be if your security policies totally prevent any access
between the domains.
Chris
Sonali wrote:
> I have architecture related question -
> I have 2 databases on 2 domains and security doesn't permit me to
> co-mingle the data. I'll be generating 2 different reports for same
> request.
> Question is - Do I need SQL server with reporting services installed
> on each domain?
> Current proposed solution is -
> Domain AAA will have SQL server with RSS
> Domain BBB will have SQL server with RSS
> Sharepoint web parts (on BBB side) will access report from AAA and
> BBB. (Domain BBB has 1 port open to allow web traffic).
> If trusted SQL server connection is made available to RSS on BBB
> side, then I think we don't need server with RSS on domain AAA. is
> this right? If so, How can I access databases from RSS across domains?
> Sounds interesing right? Please help me ....

Accessing named instance remotely

I've got an instance of SQL server running on my website. I have port
1433 open and I can connect to it via enterprise manager across the
internet just by using the domain name in the server name box.
I recently installed SQL 2K5 beta 2 on the same box and gave it a
different name. I should be able to connect to it using
domainname\instancename correct? For some reason I can't connect to
it. I guess I don't know whether this is something particular to 2K5
or not, or do I need to do something specific for any named instance?
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegr oups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>
|||You will have to specify a PORT NUMBER unless you also have UDP PORT 1434
opened on your firewall.
If you also have dynamic defined, which would not be recommended in your
configuration, you may have to open up several inbound ports to cover those
that SQL Server may use.
You would be better off blocking inbound UDP 1434, configuring your named
instance to use a specific port, say 1533, and then also open up inbound TCP
1533.
Out of curiosity, why would you expose a SQL Server installation to the
public network?
Sincerely,
Anthony Thomas

"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23AZc8EZ$EHA.2568@.TK2MSFTNGP10.phx.gbl...
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegr oups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>

Accessing named instance remotely

I've got an instance of SQL server running on my website. I have port
1433 open and I can connect to it via enterprise manager across the
internet just by using the domain name in the server name box.
I recently installed SQL 2K5 beta 2 on the same box and gave it a
different name. I should be able to connect to it using
domainname\instancename correct? For some reason I can't connect to
it. I guess I don't know whether this is something particular to 2K5
or not, or do I need to do something specific for any named instance?That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
--
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>|||You will have to specify a PORT NUMBER unless you also have UDP PORT 1434
opened on your firewall.
If you also have dynamic defined, which would not be recommended in your
configuration, you may have to open up several inbound ports to cover those
that SQL Server may use.
You would be better off blocking inbound UDP 1434, configuring your named
instance to use a specific port, say 1533, and then also open up inbound TCP
1533.
Out of curiosity, why would you expose a SQL Server installation to the
public network?
Sincerely,
Anthony Thomas
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23AZc8EZ$EHA.2568@.TK2MSFTNGP10.phx.gbl...
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
--
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>

Accessing named instance remotely

I've got an instance of SQL server running on my website. I have port
1433 open and I can connect to it via enterprise manager across the
internet just by using the domain name in the server name box.
I recently installed SQL 2K5 beta 2 on the same box and gave it a
different name. I should be able to connect to it using
domainname\instancename correct? For some reason I can't connect to
it. I guess I don't know whether this is something particular to 2K5
or not, or do I need to do something specific for any named instance?That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>|||You will have to specify a PORT NUMBER unless you also have UDP PORT 1434
opened on your firewall.
If you also have dynamic defined, which would not be recommended in your
configuration, you may have to open up several inbound ports to cover those
that SQL Server may use.
You would be better off blocking inbound UDP 1434, configuring your named
instance to use a specific port, say 1533, and then also open up inbound TCP
1533.
Out of curiosity, why would you expose a SQL Server installation to the
public network?
Sincerely,
Anthony Thomas
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23AZc8EZ$EHA.2568@.TK2MSFTNGP10.phx.gbl...
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>