Cons to seperate distributor

What are the cons of have the distribution database on its own seperate
server from the publishers with regards to transactional replication ? I am
more concerned from a latency perspective ?
Would the changes be a bit slower to propagate to the subscriber as a result
of this ?
Let me know
Using SQL 2000.
Thanks
Its very slightly slower, but the network hop isn't really detectable. The
real problem is you have introduced a single point of failure and need to
cluster the distributor as if it goes down your tlog on your publisher can
get very large very quickly.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Hassan" <Hassan@.hotmail.com> wrote in message
news:ukDRx3BQGHA.2992@.tk2msftngp13.phx.gbl...
> What are the cons of have the distribution database on its own seperate
> server from the publishers with regards to transactional replication ? I
> am more concerned from a latency perspective ?
> Would the changes be a bit slower to propagate to the subscriber as a
> result of this ?
> Let me know
> Using SQL 2000.
> Thanks
>
|||Hassan,
in terms of overall latency, using a remote distributor will be lower (ie
faster from Pub -> Sub) when there are a lot of transactions. Have a look at
this article for some stats:
http://www.microsoft.com/technet/pro.../tranrepl.mspx
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Connections

I've got a satellite group that acts as their own dba's on
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.
Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.
|||Thx but from what they're saying, it was definitely a user
process.

>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
on[vbcol=seagreen]
the[vbcol=seagreen]
all[vbcol=seagreen]
magic
>
>.
>
|||Sometimes you get "ghost connections". There are some reasons this can happen, the connection
executing an extended stored procedure is one such possibility. There can be other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel certain you have waited
long enough, recycling the SQL Server is the way to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...[vbcol=seagreen]
> Thx but from what they're saying, it was definitely a user
> process.
> (typically spid>50) that
> what they're seeing.
> message
> on
> the
> all
> magic

Connections

I've got a satellite group that acts as their own dba's on
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.|||Thx but from what they're saying, it was definitely a user
process.

>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
on[vbcol=seagreen]
the[vbcol=seagreen]
all[vbcol=seagreen]
magic[vbcol=seagreen]
>
>.
>|||Sometimes you get "ghost connections". There are some reasons this can happe
n, the connection
executing an extended stored procedure is one such possibility. There can be
other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it
will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel
certain you have waited
long enough, recycling the SQL Server is the way to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...[vbcol=seagreen]
> Thx but from what they're saying, it was definitely a user
> process.
>
> (typically spid>50) that
> what they're seeing.
> message
> on
> the
> all
> magic

Connections

I've got a satellite group that acts as their own dba's on
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.|||Thx but from what they're saying, it was definitely a user
process.
>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
>> I've got a satellite group that acts as their own dba's
on
>> a 7.0 server. They claim that they cannot kill certain
>> connections, i.e. they typed in kill and nothing
>> happened. I have seen that happen with web-based
>> connection pooling apps but not with a regular app that
>> they're working with.
>> Anyway, what I wanted to ask is: is the kill command
the
>> only way to kill a connection besides the winner-take-
all
>> methods of taking the database offline or stopping and
>> restarting services? Just wondering if there's some
magic
>> bullet that I hadn't heard of.
>
>.
>|||Sometimes you get "ghost connections". There are some reasons this can happen, the connection
executing an extended stored procedure is one such possibility. There can be other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel certain you have waited
long enough, recycling the SQL Server is the way to go.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...
> Thx but from what they're saying, it was definitely a user
> process.
> >--Original Message--
> >Kill can only be used to terminate user processes
> (typically spid>50) that
> >is not executing an extended procedure. Perhaps, that's
> what they're seeing.
> >
> >
> >"NTel" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> >> I've got a satellite group that acts as their own dba's
> on
> >> a 7.0 server. They claim that they cannot kill certain
> >> connections, i.e. they typed in kill and nothing
> >> happened. I have seen that happen with web-based
> >> connection pooling apps but not with a regular app that
> >> they're working with.
> >>
> >> Anyway, what I wanted to ask is: is the kill command
> the
> >> only way to kill a connection besides the winner-take-
> all
> >> methods of taking the database offline or stopping and
> >> restarting services? Just wondering if there's some
> magic
> >> bullet that I hadn't heard of.
> >
> >
> >.
> >

Connection String Error

Hi Team

I am new to WEB sites as I normal work with Win apps.

I am using Server 2003 with SQL server 2005 Delevoper.

The server is on my own network in the same room..

I have made a new Web Site in Visual Studio 2005 DotNet Framework 2.0. It runs fine on testing.

I can log in and move around just fine. BUT when I publish it to the server the following happens:

I Can find the web site in internet explore from my Domain name (www.rbsoft.com.au) or Static IP. I get the default page up ok.

Then when I click on login I will get the login page. So I fill it in and click Login.

Then I get the follwing Error message.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

The Connection string is as follows:

<connectionStrings>

<add name="ConnectionString" connectionString="Data Source=RBSOFT-SERVER\MSSQLSERVER;AttachDbFilename=\App_Date\ASPNETDB.MDF;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>

</connectionStrings>

I seems to me that the web site can not find the ASPNETDB.MDF database.

I can see the database on the server with "SQL Server Management Studio Express"

I spent many hours trying to find out why it will not work.

Can any one help me - Please

Regards

Ron B

please check spelling of \App_Date\*.mdf
DatE or Data

connection problems to a SQL2005 DB that I own

I am a DB owner/ creator. I have connected to the DB before through my ASP.net app in the server explorer. Now when I try to refresh the connection I get an error message that says "User does not have permission to perform this action." I cannot figure out why because my connection string has not changed and my DB is still in the same location as it was before. I have checked all of the permissions on the SQL Server management studio and I have permissions to do everything. PLEASE HELP! :(

This has nothing to do with connection string ...

You must check the priviliges granted to the user from which you have logged into your data base.

|||

tabish82:

This has nothing to do with connection string ...

You must check the priviliges granted to the user from which you have logged into your data base.

As I said in the above post...

"I have checked all of the permissions on the SQL Server management studio and I have permissions to do everything"

I have not changed any of the permissions or used a different log on to access the db. I still cannot get connected.

|||

Check out:

http://blogs.msdn.com/kaelr/archive/2005/10/28/486369.aspx

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

Hope it helps...

|||

There might be some changes in the network configuration (e.g. Firewall).

Try to disable your firewall on Windows and try again.

Good luck.

|||

I have all firewall settings disabled, but thanks anyway

|||

Can you register (or connect to) your database server using same UserID and Password?

|||

Do you have a linked server?

I hope this will help:

http://blogs.msdn.com/kaelr/archive/2005/10/28/486369.aspx

http://www.aspspider.com/qa/ViewQuestion.aspx?QuestionId=1032

Good luck.