Dear All,
We are getting a lot of sleeping (and orphan) connections
to our database, so I would like to create a script to
kill them based upon them being sleeping for over 2 hours.
Can anyone point me to the table that holds this info ?
I don't want the script as I will be trying that myself.
TIA
JimThe table is master.dbo.sysprocesses...
Sleeping is not bad... It simply means that the connection is open but not
currently doing any work... Most connections will be in this state most of
the time. Also consider the effect of connection pooling...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:351b01c48f4a$17717580$a601280a@.phx.gbl...
> Dear All,
> We are getting a lot of sleeping (and orphan) connections
> to our database, so I would like to create a script to
> kill them based upon them being sleeping for over 2 hours.
> Can anyone point me to the table that holds this info ?
> I don't want the script as I will be trying that myself.
> TIA
> Jim
>|||Thanks Wayne,
In our case its usually because the data objects have made
a new connection, so what we have is a lot of unused
connections by the same person. Its those it want to get
rid of.
Thanks
Jim
>--Original Message--
>The table is master.dbo.sysprocesses...
>Sleeping is not bad... It simply means that the
connection is open but not
>currently doing any work... Most connections will be in
this state most of
>the time. Also consider the effect of connection
pooling...
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Jimbo" <anonymous@.discussions.microsoft.com> wrote in
message
>news:351b01c48f4a$17717580$a601280a@.phx.gbl...
>> Dear All,
>> We are getting a lot of sleeping (and orphan)
connections
>> to our database, so I would like to create a script to
>> kill them based upon them being sleeping for over 2
hours.
>> Can anyone point me to the table that holds this info ?
>> I don't want the script as I will be trying that myself.
>> TIA
>> Jim
>>
>
>.
>|||If that's the case, either your programmers aren't properly cleaning up the
connections, or these connections are still in use by the data objects and
you'll cause headaches for your developers if you take this path.
Personally, I'd make them perform a code review and fix the problem - most
connection leaks are due to sloppy coding practices.
--
Michael D. Long
Microsoft MVP - Windows SDK
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:376e01c48f66$403ea520$a301280a@.phx.gbl...
> Thanks Wayne,
> In our case its usually because the data objects have made
> a new connection, so what we have is a lot of unused
> connections by the same person. Its those it want to get
> rid of.
> Thanks
> Jim
>
> >--Original Message--
> >The table is master.dbo.sysprocesses...
> >
> >Sleeping is not bad... It simply means that the
> connection is open but not
> >currently doing any work... Most connections will be in
> this state most of
> >the time. Also consider the effect of connection
> pooling...
> >
> >--
> >Wayne Snyder, MCDBA, SQL Server MVP
> >Mariner, Charlotte, NC
> >www.mariner-usa.com
> >(Please respond only to the newsgroups.)
> >
> >I support the Professional Association of SQL Server
> (PASS) and it's
> >community of SQL Server professionals.
> >www.sqlpass.org
> >
> >"Jimbo" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:351b01c48f4a$17717580$a601280a@.phx.gbl...
> >> Dear All,
> >> We are getting a lot of sleeping (and orphan)
> connections
> >> to our database, so I would like to create a script to
> >> kill them based upon them being sleeping for over 2
> hours.
> >>
> >> Can anyone point me to the table that holds this info ?
> >>
> >> I don't want the script as I will be trying that myself.
> >>
> >> TIA
> >> Jim
> >>
> >>
> >
> >
> >.
> >sqlsql
Showing posts with label connections. Show all posts
Showing posts with label connections. Show all posts
Tuesday, March 20, 2012
Connections...
Dear All,
SQL Server 2000, Service Pack 3a
We have a problem with locking where as soon as something deadlocks the
application fails.
There are two solutions that spring to mind, either totally re-writing the
Application or setting the SET LOCK_TIMEOUT command.
Now currently we cannot do the re-write as the developers don't have time (I
was out voted) so we are looking to the Set Lock_Timeout, but here is the
problem.
The Connections used are set by JBOSS and our developers cannot find a way
of setting the SET LOCK_TIMEOUT to the connection through JBOSS.
What I was wondering then was is there a way through SQL, i.e. Whenever a
connection is created it automatically does a SET LOCK_TIMEOUT ?
If not could someone go through how a connection is actually created?, so I
can attempt to put a trigger somewhere.
I would totally agree that this is a 'hack' fix and does not solve the
underlying problem but they want a quick fix :(
JJulie,
changing the Lock timeout won't solve you're problem. The Lock timeout
only defines how long a query wait for a resource until a exlusive lock
is released. By default a query waits indefinetely until the lock is
released.
Deadlocks are different. SQL Server detects if a deadlock occurs and
the kills one process, the deadlock victim. This happens very fast, so
the time the resource is locked would be shorter than your timeout.
You need to catch the error 1205 and the handle it in your application.
I don't think there's a alternative for that.
Markus
SQL Server 2000, Service Pack 3a
We have a problem with locking where as soon as something deadlocks the
application fails.
There are two solutions that spring to mind, either totally re-writing the
Application or setting the SET LOCK_TIMEOUT command.
Now currently we cannot do the re-write as the developers don't have time (I
was out voted) so we are looking to the Set Lock_Timeout, but here is the
problem.
The Connections used are set by JBOSS and our developers cannot find a way
of setting the SET LOCK_TIMEOUT to the connection through JBOSS.
What I was wondering then was is there a way through SQL, i.e. Whenever a
connection is created it automatically does a SET LOCK_TIMEOUT ?
If not could someone go through how a connection is actually created?, so I
can attempt to put a trigger somewhere.
I would totally agree that this is a 'hack' fix and does not solve the
underlying problem but they want a quick fix :(
JJulie,
changing the Lock timeout won't solve you're problem. The Lock timeout
only defines how long a query wait for a resource until a exlusive lock
is released. By default a query waits indefinetely until the lock is
released.
Deadlocks are different. SQL Server detects if a deadlock occurs and
the kills one process, the deadlock victim. This happens very fast, so
the time the resource is locked would be shorter than your timeout.
You need to catch the error 1205 and the handle it in your application.
I don't think there's a alternative for that.
Markus
Connections...
Dear All,
SQL Server 2000, Service Pack 3a
We have a problem with locking where as soon as something deadlocks the
application fails.
There are two solutions that spring to mind, either totally re-writing the
Application or setting the SET LOCK_TIMEOUT command.
Now currently we cannot do the re-write as the developers don't have time (I
was out voted) so we are looking to the Set Lock_Timeout, but here is the
problem.
The Connections used are set by JBOSS and our developers cannot find a way
of setting the SET LOCK_TIMEOUT to the connection through JBOSS.
What I was wondering then was is there a way through SQL, i.e. Whenever a
connection is created it automatically does a SET LOCK_TIMEOUT ?
If not could someone go through how a connection is actually created?, so I
can attempt to put a trigger somewhere.
I would totally agree that this is a 'hack' fix and does not solve the
underlying problem but they want a quick fix
JJulie,
changing the Lock timeout won't solve you're problem. The Lock timeout
only defines how long a query wait for a resource until a exlusive lock
is released. By default a query waits indefinetely until the lock is
released.
Deadlocks are different. SQL Server detects if a deadlock occurs and
the kills one process, the deadlock victim. This happens very fast, so
the time the resource is locked would be shorter than your timeout.
You need to catch the error 1205 and the handle it in your application.
I don't think there's a alternative for that.
Markus
SQL Server 2000, Service Pack 3a
We have a problem with locking where as soon as something deadlocks the
application fails.
There are two solutions that spring to mind, either totally re-writing the
Application or setting the SET LOCK_TIMEOUT command.
Now currently we cannot do the re-write as the developers don't have time (I
was out voted) so we are looking to the Set Lock_Timeout, but here is the
problem.
The Connections used are set by JBOSS and our developers cannot find a way
of setting the SET LOCK_TIMEOUT to the connection through JBOSS.
What I was wondering then was is there a way through SQL, i.e. Whenever a
connection is created it automatically does a SET LOCK_TIMEOUT ?
If not could someone go through how a connection is actually created?, so I
can attempt to put a trigger somewhere.
I would totally agree that this is a 'hack' fix and does not solve the
underlying problem but they want a quick fix
JJulie,
changing the Lock timeout won't solve you're problem. The Lock timeout
only defines how long a query wait for a resource until a exlusive lock
is released. By default a query waits indefinetely until the lock is
released.
Deadlocks are different. SQL Server detects if a deadlock occurs and
the kills one process, the deadlock victim. This happens very fast, so
the time the resource is locked would be shorter than your timeout.
You need to catch the error 1205 and the handle it in your application.
I don't think there's a alternative for that.
Markus
Connections...
Dear All,
We are getting a lot of sleeping (and orphan) connections
to our database, so I would like to create a script to
kill them based upon them being sleeping for over 2 hours.
Can anyone point me to the table that holds this info ?
I don't want the script as I will be trying that myself.
TIA
JimThe table is master.dbo.sysprocesses...
Sleeping is not bad... It simply means that the connection is open but not
currently doing any work... Most connections will be in this state most of
the time. Also consider the effect of connection pooling...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:351b01c48f4a$17717580$a601280a@.phx.gbl...
> Dear All,
> We are getting a lot of sleeping (and orphan) connections
> to our database, so I would like to create a script to
> kill them based upon them being sleeping for over 2 hours.
> Can anyone point me to the table that holds this info ?
> I don't want the script as I will be trying that myself.
> TIA
> Jim
>|||Thanks Wayne,
In our case its usually because the data objects have made
a new connection, so what we have is a lot of unused
connections by the same person. Its those it want to get
rid of.
Thanks
Jim
>--Original Message--
>The table is master.dbo.sysprocesses...
>Sleeping is not bad... It simply means that the
connection is open but not
>currently doing any work... Most connections will be in
this state most of
>the time. Also consider the effect of connection
pooling...
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Jimbo" <anonymous@.discussions.microsoft.com> wrote in
message
>news:351b01c48f4a$17717580$a601280a@.phx.gbl...
connections[vbcol=seagreen]
hours.[vbcol=seagreen]
>
>.
>|||If that's the case, either your programmers aren't properly cleaning up the
connections, or these connections are still in use by the data objects and
you'll cause headaches for your developers if you take this path.
Personally, I'd make them perform a code review and fix the problem - most
connection leaks are due to sloppy coding practices.
Michael D. Long
Microsoft MVP - Windows SDK
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:376e01c48f66$403ea520$a301280a@.phx.gbl...[vbcol=seagreen]
> Thanks Wayne,
> In our case its usually because the data objects have made
> a new connection, so what we have is a lot of unused
> connections by the same person. Its those it want to get
> rid of.
> Thanks
> Jim
>
> connection is open but not
> this state most of
> pooling...
> (PASS) and it's
> message
> connections
> hours.
We are getting a lot of sleeping (and orphan) connections
to our database, so I would like to create a script to
kill them based upon them being sleeping for over 2 hours.
Can anyone point me to the table that holds this info ?
I don't want the script as I will be trying that myself.
TIA
JimThe table is master.dbo.sysprocesses...
Sleeping is not bad... It simply means that the connection is open but not
currently doing any work... Most connections will be in this state most of
the time. Also consider the effect of connection pooling...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:351b01c48f4a$17717580$a601280a@.phx.gbl...
> Dear All,
> We are getting a lot of sleeping (and orphan) connections
> to our database, so I would like to create a script to
> kill them based upon them being sleeping for over 2 hours.
> Can anyone point me to the table that holds this info ?
> I don't want the script as I will be trying that myself.
> TIA
> Jim
>|||Thanks Wayne,
In our case its usually because the data objects have made
a new connection, so what we have is a lot of unused
connections by the same person. Its those it want to get
rid of.
Thanks
Jim
>--Original Message--
>The table is master.dbo.sysprocesses...
>Sleeping is not bad... It simply means that the
connection is open but not
>currently doing any work... Most connections will be in
this state most of
>the time. Also consider the effect of connection
pooling...
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Jimbo" <anonymous@.discussions.microsoft.com> wrote in
message
>news:351b01c48f4a$17717580$a601280a@.phx.gbl...
connections[vbcol=seagreen]
hours.[vbcol=seagreen]
>
>.
>|||If that's the case, either your programmers aren't properly cleaning up the
connections, or these connections are still in use by the data objects and
you'll cause headaches for your developers if you take this path.
Personally, I'd make them perform a code review and fix the problem - most
connection leaks are due to sloppy coding practices.
Michael D. Long
Microsoft MVP - Windows SDK
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:376e01c48f66$403ea520$a301280a@.phx.gbl...[vbcol=seagreen]
> Thanks Wayne,
> In our case its usually because the data objects have made
> a new connection, so what we have is a lot of unused
> connections by the same person. Its those it want to get
> rid of.
> Thanks
> Jim
>
> connection is open but not
> this state most of
> pooling...
> (PASS) and it's
> message
> connections
> hours.
Connections...
Dear All,
We are getting a lot of sleeping (and orphan) connections
to our database, so I would like to create a script to
kill them based upon them being sleeping for over 2 hours.
Can anyone point me to the table that holds this info ?
I don't want the script as I will be trying that myself.
TIA
Jim
The table is master.dbo.sysprocesses...
Sleeping is not bad... It simply means that the connection is open but not
currently doing any work... Most connections will be in this state most of
the time. Also consider the effect of connection pooling...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:351b01c48f4a$17717580$a601280a@.phx.gbl...
> Dear All,
> We are getting a lot of sleeping (and orphan) connections
> to our database, so I would like to create a script to
> kill them based upon them being sleeping for over 2 hours.
> Can anyone point me to the table that holds this info ?
> I don't want the script as I will be trying that myself.
> TIA
> Jim
>
|||Thanks Wayne,
In our case its usually because the data objects have made
a new connection, so what we have is a lot of unused
connections by the same person. Its those it want to get
rid of.
Thanks
Jim
>--Original Message--
>The table is master.dbo.sysprocesses...
>Sleeping is not bad... It simply means that the
connection is open but not
>currently doing any work... Most connections will be in
this state most of
>the time. Also consider the effect of connection
pooling...
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Jimbo" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:351b01c48f4a$17717580$a601280a@.phx.gbl...
connections[vbcol=seagreen]
hours.
>
>.
>
|||If that's the case, either your programmers aren't properly cleaning up the
connections, or these connections are still in use by the data objects and
you'll cause headaches for your developers if you take this path.
Personally, I'd make them perform a code review and fix the problem - most
connection leaks are due to sloppy coding practices.
Michael D. Long
Microsoft MVP - Windows SDK
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:376e01c48f66$403ea520$a301280a@.phx.gbl...[vbcol=seagreen]
> Thanks Wayne,
> In our case its usually because the data objects have made
> a new connection, so what we have is a lot of unused
> connections by the same person. Its those it want to get
> rid of.
> Thanks
> Jim
>
> connection is open but not
> this state most of
> pooling...
> (PASS) and it's
> message
> connections
> hours.
We are getting a lot of sleeping (and orphan) connections
to our database, so I would like to create a script to
kill them based upon them being sleeping for over 2 hours.
Can anyone point me to the table that holds this info ?
I don't want the script as I will be trying that myself.
TIA
Jim
The table is master.dbo.sysprocesses...
Sleeping is not bad... It simply means that the connection is open but not
currently doing any work... Most connections will be in this state most of
the time. Also consider the effect of connection pooling...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:351b01c48f4a$17717580$a601280a@.phx.gbl...
> Dear All,
> We are getting a lot of sleeping (and orphan) connections
> to our database, so I would like to create a script to
> kill them based upon them being sleeping for over 2 hours.
> Can anyone point me to the table that holds this info ?
> I don't want the script as I will be trying that myself.
> TIA
> Jim
>
|||Thanks Wayne,
In our case its usually because the data objects have made
a new connection, so what we have is a lot of unused
connections by the same person. Its those it want to get
rid of.
Thanks
Jim
>--Original Message--
>The table is master.dbo.sysprocesses...
>Sleeping is not bad... It simply means that the
connection is open but not
>currently doing any work... Most connections will be in
this state most of
>the time. Also consider the effect of connection
pooling...
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Jimbo" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:351b01c48f4a$17717580$a601280a@.phx.gbl...
connections[vbcol=seagreen]
hours.
>
>.
>
|||If that's the case, either your programmers aren't properly cleaning up the
connections, or these connections are still in use by the data objects and
you'll cause headaches for your developers if you take this path.
Personally, I'd make them perform a code review and fix the problem - most
connection leaks are due to sloppy coding practices.
Michael D. Long
Microsoft MVP - Windows SDK
"Jimbo" <anonymous@.discussions.microsoft.com> wrote in message
news:376e01c48f66$403ea520$a301280a@.phx.gbl...[vbcol=seagreen]
> Thanks Wayne,
> In our case its usually because the data objects have made
> a new connection, so what we have is a lot of unused
> connections by the same person. Its those it want to get
> rid of.
> Thanks
> Jim
>
> connection is open but not
> this state most of
> pooling...
> (PASS) and it's
> message
> connections
> hours.
Connections to the DB
Hi,
Is there a way of finding if there are connections to a SQL Database with T-SQL?
Is there a way of finding if there are connections to a SQL Database with T-SQL?
I am writing a routine that will crate a copy of the main Database files and to do this i needed to make sure that there are no other uses connected before i Unattach the DB and copy the files.
It would also be useful if i can tell the end user which user are connected.select * from master.sys.syslogins
_
? www.carlop.com × carlop-dev.blogspot.com
sqlsqlConnections to SQL server are slow on one machine
Hi all,
My client PC is very slow to connect to all SQL server databases.
Other client machines are having no problem at all. I even tried
connecting to my local MSDE database, and the same behavior results.
If I try to connect via a .NET application it is also slow.
My client PC is very slow to connect to all SQL server databases.
Other client machines are having no problem at all. I even tried
connecting to my local MSDE database, and the same behavior results.
If I try to connect via a .NET application it is also slow.
The connection is always made if I wait long enough, but then when I go
to query a table it is very slow again, even if I'm only returning one
row from a table with 5 fields.
Does anyone have any suggestions on how to troubleshoot this?
Thanks.check whether the ping time are different too ...
try switching off local firewall ...
"foreman_bob" <smhceh@.gmail.com> schrieb im Newsbeitrag
news:1137940934.406196.284270@.g47g2000cwa.googlegr oups.com...
> Hi all,
> My client PC is very slow to connect to all SQL server databases.
> Other client machines are having no problem at all. I even tried
> connecting to my local MSDE database, and the same behavior results.
> If I try to connect via a .NET application it is also slow.
> The connection is always made if I wait long enough, but then when I go
> to query a table it is very slow again, even if I'm only returning one
> row from a table with 5 fields.
> Does anyone have any suggestions on how to troubleshoot this?
> Thanks.|||What net library are you using? Is it the same net lib as the other
people that don't have issues? Are you authenticating the same way?Are
you requesting SSL or multiprotocol encryption from the client? Are
you located on the same LAN as the other users or do you dialup through
your 28KB modem into a VPN connection?
Greg|||I found out what was causing my problem today. I had ODBC tracing
turned on. As soon as I turned it off everything was fine.
Thanks for your replies.
Greg wrote:
> What net library are you using? Is it the same net lib as the other
> people that don't have issues? Are you authenticating the same way?Are
> you requesting SSL or multiprotocol encryption from the client? Are
> you located on the same LAN as the other users or do you dialup through
> your 28KB modem into a VPN connection?
> Greg|||wow.
Thank you! I am filing this one off!!!! I can totally see myself
turning it on, wandering off and forgetting it is on.
ick.
Connections to SQL Server
I have been developing an Intranet for the past few months, and now that I
have developed about 4 apps, I am questioning my connection string. We have
a Windows 2000 Server with SQL Server 2000 and are using Integrated Auth. so
that people don't have to login to the sql server.
Here is my current connection string,
MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Data
Source=swvtc06;Initial Catalog=CliCore;"
As you can see I am using Trusted Connection, which is the only way that I
could get this connection to work. If I remove the trusted connection info,
it doesn't work at all.
How should I go about setting this up? Why is using trusted connection such
a bad idea? It seems to work, if someone doesn't have permission, it
doesn't let them into the db. And, what are the other ways of doing this?
Thanks,
Drew LaingHi Drew,
Your connection should read as follows:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False
I use this string in a delphi ado connection component to set up a trusted c
onnection to my database server.
Regards,
Ruud Aalders
have developed about 4 apps, I am questioning my connection string. We have
a Windows 2000 Server with SQL Server 2000 and are using Integrated Auth. so
that people don't have to login to the sql server.
Here is my current connection string,
MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Data
Source=swvtc06;Initial Catalog=CliCore;"
As you can see I am using Trusted Connection, which is the only way that I
could get this connection to work. If I remove the trusted connection info,
it doesn't work at all.
How should I go about setting this up? Why is using trusted connection such
a bad idea? It seems to work, if someone doesn't have permission, it
doesn't let them into the db. And, what are the other ways of doing this?
Thanks,
Drew LaingHi Drew,
Your connection should read as follows:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False
I use this string in a delphi ado connection component to set up a trusted c
onnection to my database server.
Regards,
Ruud Aalders
quote:
Originally posted by Drew
I have been developing an Intranet for the past few months, and now that I
have developed about 4 apps, I am questioning my connection string. We have
a Windows 2000 Server with SQL Server 2000 and are using Integrated Auth. so
that people don't have to login to the sql server.
Here is my current connection string,
MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Data
Source=swvtc06;Initial Catalog=CliCore;"
As you can see I am using Trusted Connection, which is the only way that I
could get this connection to work. If I remove the trusted connection info,
it doesn't work at all.
How should I go about setting this up? Why is using trusted connection such
a bad idea? It seems to work, if someone doesn't have permission, it
doesn't let them into the db. And, what are the other ways of doing this?
Thanks,
Drew Laing
Connections to SQL Server
I have been developing an Intranet for the past few months, and now that I
have developed about 4 apps, I am questioning my connection string. We have
a Windows 2000 Server with SQL Server 2000 and are using Integrated Auth. so
that people don't have to login to the sql server.
Here is my current connection string,
MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Data
Source=swvtc06;Initial Catalog=CliCore;"
As you can see I am using Trusted Connection, which is the only way that I
could get this connection to work. If I remove the trusted connection info,
it doesn't work at all.
How should I go about setting this up? Why is using trusted connection such
a bad idea? It seems to work, if someone doesn't have permission, it
doesn't let them into the db. And, what are the other ways of doing this?
Thanks,
Drew LaingHi Drew,
Your connection should read as follows:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Securit
Info=False
I use this string in a delphi ado connection component to set up
trusted connection to my database server.
Regards,
Ruud Aalders
Drew wrote:
> *I have been developing an Intranet for the past few months, and no
> that I
> have developed about 4 apps, I am questioning my connection string.
> We have
> a Windows 2000 Server with SQL Server 2000 and are using Integrate
> Auth. so
> that people don't have to login to the sql server.
> Here is my current connection string,
> MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Data
> Source=swvtc06;Initial Catalog=CliCore;"
> As you can see I am using Trusted Connection, which is the only wa
> that I
> could get this connection to work. If I remove the truste
> connection info,
> it doesn't work at all.
> How should I go about setting this up? Why is using truste
> connection such
> a bad idea? It seems to work, if someone doesn't have permission
> it
> doesn't let them into the db. And, what are the other ways of doin
> this?
> Thanks,
> Drew Laing
-
Ruud Aalder
----
Posted via http://www.webservertalk.co
----
View this thread: http://www.webservertalk.com/message462636.htm
have developed about 4 apps, I am questioning my connection string. We have
a Windows 2000 Server with SQL Server 2000 and are using Integrated Auth. so
that people don't have to login to the sql server.
Here is my current connection string,
MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Data
Source=swvtc06;Initial Catalog=CliCore;"
As you can see I am using Trusted Connection, which is the only way that I
could get this connection to work. If I remove the trusted connection info,
it doesn't work at all.
How should I go about setting this up? Why is using trusted connection such
a bad idea? It seems to work, if someone doesn't have permission, it
doesn't let them into the db. And, what are the other ways of doing this?
Thanks,
Drew LaingHi Drew,
Your connection should read as follows:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Securit
Info=False
I use this string in a delphi ado connection component to set up
trusted connection to my database server.
Regards,
Ruud Aalders
Drew wrote:
> *I have been developing an Intranet for the past few months, and no
> that I
> have developed about 4 apps, I am questioning my connection string.
> We have
> a Windows 2000 Server with SQL Server 2000 and are using Integrate
> Auth. so
> that people don't have to login to the sql server.
> Here is my current connection string,
> MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Data
> Source=swvtc06;Initial Catalog=CliCore;"
> As you can see I am using Trusted Connection, which is the only wa
> that I
> could get this connection to work. If I remove the truste
> connection info,
> it doesn't work at all.
> How should I go about setting this up? Why is using truste
> connection such
> a bad idea? It seems to work, if someone doesn't have permission
> it
> doesn't let them into the db. And, what are the other ways of doin
> this?
> Thanks,
> Drew Laing
-
Ruud Aalder
----
Posted via http://www.webservertalk.co
----
View this thread: http://www.webservertalk.com/message462636.htm
connections to SQL Server
Hi All,
I need to put a script together that would tell me how many connections to SQL Server there are at any given time. Which table would store this info?
Thanks.Define what you mean by connections, and which version of SQL Server you are targeting. One simplistic answer for SQL 2000 would be:SELECT Count(DISTINCT spid)
FROM master.dbo.sysprocesses
WHERE 50 < spid-PatP|||The information from the sp_who/sp_who2 stored procedures might also be useful...
I need to put a script together that would tell me how many connections to SQL Server there are at any given time. Which table would store this info?
Thanks.Define what you mean by connections, and which version of SQL Server you are targeting. One simplistic answer for SQL 2000 would be:SELECT Count(DISTINCT spid)
FROM master.dbo.sysprocesses
WHERE 50 < spid-PatP|||The information from the sp_who/sp_who2 stored procedures might also be useful...
Connections to SQL Server
I have been developing an Intranet for the past few months, and now that I
have developed about 4 apps, I am questioning my connection string. We have
a Windows 2000 Server with SQL Server 2000 and are using Integrated Auth. so
that people don't have to login to the sql server.
Here is my current connection string,
MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Da ta
Source=swvtc06;Initial Catalog=CliCore;"
As you can see I am using Trusted Connection, which is the only way that I
could get this connection to work. If I remove the trusted connection info,
it doesn't work at all.
How should I go about setting this up? Why is using trusted connection such
a bad idea? It seems to work, if someone doesn't have permission, it
doesn't let them into the db. And, what are the other ways of doing this?
Thanks,
Drew Laing
Hi Drew,
Your connection should read as follows:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False
I use this string in a delphi ado connection component to set up a
trusted connection to my database server.
Regards,
Ruud Aalders
Drew wrote:
> *I have been developing an Intranet for the past few months, and now
> that I
> have developed about 4 apps, I am questioning my connection string.
> We have
> a Windows 2000 Server with SQL Server 2000 and are using Integrated
> Auth. so
> that people don't have to login to the sql server.
> Here is my current connection string,
> MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Da ta
> Source=swvtc06;Initial Catalog=CliCore;"
> As you can see I am using Trusted Connection, which is the only way
> that I
> could get this connection to work. If I remove the trusted
> connection info,
> it doesn't work at all.
> How should I go about setting this up? Why is using trusted
> connection such
> a bad idea? It seems to work, if someone doesn't have permission,
> it
> doesn't let them into the db. And, what are the other ways of doing
> this?
> Thanks,
> Drew Laing *
Ruud Aalders
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message462636.html
sqlsql
have developed about 4 apps, I am questioning my connection string. We have
a Windows 2000 Server with SQL Server 2000 and are using Integrated Auth. so
that people don't have to login to the sql server.
Here is my current connection string,
MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Da ta
Source=swvtc06;Initial Catalog=CliCore;"
As you can see I am using Trusted Connection, which is the only way that I
could get this connection to work. If I remove the trusted connection info,
it doesn't work at all.
How should I go about setting this up? Why is using trusted connection such
a bad idea? It seems to work, if someone doesn't have permission, it
doesn't let them into the db. And, what are the other ways of doing this?
Thanks,
Drew Laing
Hi Drew,
Your connection should read as follows:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False
I use this string in a delphi ado connection component to set up a
trusted connection to my database server.
Regards,
Ruud Aalders
Drew wrote:
> *I have been developing an Intranet for the past few months, and now
> that I
> have developed about 4 apps, I am questioning my connection string.
> We have
> a Windows 2000 Server with SQL Server 2000 and are using Integrated
> Auth. so
> that people don't have to login to the sql server.
> Here is my current connection string,
> MM_CliCore_STRING = "Provider=SQLOLEDB.1;Trusted_Connection=Yes;Da ta
> Source=swvtc06;Initial Catalog=CliCore;"
> As you can see I am using Trusted Connection, which is the only way
> that I
> could get this connection to work. If I remove the trusted
> connection info,
> it doesn't work at all.
> How should I go about setting this up? Why is using trusted
> connection such
> a bad idea? It seems to work, if someone doesn't have permission,
> it
> doesn't let them into the db. And, what are the other ways of doing
> this?
> Thanks,
> Drew Laing *
Ruud Aalders
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message462636.html
sqlsql
connections to MSDE with .net installed
Hi,
Does the .net framework take up a connection to MSDE when starting up? We
are experiencing the following scenario:
Start up computer
Start our program that uses MSDE and the .net framework
Runs very slow
Shut down program on all computers
Stop MSDE service and Start again and it runs fine.
The reason I ask about the .net framework is that our program ran fine
before we migrated it to .net.
It seems like the govenor kicks in as soon as the machine is started - maybe
..net checks liscences or something?
..Net does not automatically take up connections or check licenses to MSDE or
any other DBMS. Run SQL Profiler (you have the Developers Edition of SQL
Server, don't you?) and see if any unexpected connections are being made to
the MSDE instance.
Jim
"Andrew" <Andrew@.discussions.microsoft.com> wrote in message
news:BF7838CC-CC14-4953-82A4-280A7B8213F7@.microsoft.com...
> Hi,
> Does the .net framework take up a connection to MSDE when starting up? We
> are experiencing the following scenario:
> Start up computer
> Start our program that uses MSDE and the .net framework
> Runs very slow
> Shut down program on all computers
> Stop MSDE service and Start again and it runs fine.
> The reason I ask about the .net framework is that our program ran fine
> before we migrated it to .net.
> It seems like the govenor kicks in as soon as the machine is started -
maybe
> .net checks liscences or something?
Does the .net framework take up a connection to MSDE when starting up? We
are experiencing the following scenario:
Start up computer
Start our program that uses MSDE and the .net framework
Runs very slow
Shut down program on all computers
Stop MSDE service and Start again and it runs fine.
The reason I ask about the .net framework is that our program ran fine
before we migrated it to .net.
It seems like the govenor kicks in as soon as the machine is started - maybe
..net checks liscences or something?
..Net does not automatically take up connections or check licenses to MSDE or
any other DBMS. Run SQL Profiler (you have the Developers Edition of SQL
Server, don't you?) and see if any unexpected connections are being made to
the MSDE instance.
Jim
"Andrew" <Andrew@.discussions.microsoft.com> wrote in message
news:BF7838CC-CC14-4953-82A4-280A7B8213F7@.microsoft.com...
> Hi,
> Does the .net framework take up a connection to MSDE when starting up? We
> are experiencing the following scenario:
> Start up computer
> Start our program that uses MSDE and the .net framework
> Runs very slow
> Shut down program on all computers
> Stop MSDE service and Start again and it runs fine.
> The reason I ask about the .net framework is that our program ran fine
> before we migrated it to .net.
> It seems like the govenor kicks in as soon as the machine is started -
maybe
> .net checks liscences or something?
Connections Timing Out
I am running an application on MS SQL2000 SP4. I have 5 clients connecting to
the SQL server. Almost every night between 5
pm and 6:30pm, I lose the
connection to the server from the clients and I get a message about my
database possibly being compromised. Everything locks up and I must reboot
the client.
Has any one experienced this?
Fini2549
Check to see if there are any scheduled jobs running at that time. Sounds
like someone is running a DBCC CHECKDB and placing the db in single user
mode.
Andrew J. Kelly SQL MVP
"Fini2549" <Fini2549@.discussions.microsoft.com> wrote in message
news:9990B03B-CE13-4CEB-9EF8-E4FFB68E0A10@.microsoft.com...
>I am running an application on MS SQL2000 SP4. I have 5 clients connecting
>to
> the SQL server. Almost every night between 5pm and 6:30pm, I lose the
> connection to the server from the clients and I get a message about my
> database possibly being compromised. Everything locks up and I must reboot
> the client.
> Has any one experienced this?
> Fini2549
the SQL server. Almost every night between 5
pm and 6:30pm, I lose theconnection to the server from the clients and I get a message about my
database possibly being compromised. Everything locks up and I must reboot
the client.
Has any one experienced this?
Fini2549
Check to see if there are any scheduled jobs running at that time. Sounds
like someone is running a DBCC CHECKDB and placing the db in single user
mode.
Andrew J. Kelly SQL MVP
"Fini2549" <Fini2549@.discussions.microsoft.com> wrote in message
news:9990B03B-CE13-4CEB-9EF8-E4FFB68E0A10@.microsoft.com...
>I am running an application on MS SQL2000 SP4. I have 5 clients connecting
>to
> the SQL server. Almost every night between 5
pm and 6:30pm, I lose the> connection to the server from the clients and I get a message about my
> database possibly being compromised. Everything locks up and I must reboot
> the client.
> Has any one experienced this?
> Fini2549
Connections Timed-Out
Hello, All!
Good Afternoon!
I'm having a strange situation in my SQL SErver 2000 SP3a with 4 Processors,
4GB of RAM and high-end disk sub-system.
I migrate a specific database from another instance with SQL SErver 2000 SP3a
too to this new server with more hardware resource than another one.
The application that access this DataBase stablish a connection with SQL
SErver using TCP/IP, everything works fine. So, if I let the connection
"sleeping", or better, if I let the connection idle for amount of time, I
need to stablish the connection to ther SQL SErver again.
I hadn't the same situation in the old instance as I having. I think that
it's happening because the other instance was dedicated to this application
and that new Instance don't.
In this new Instance I have many other connections simultaneously, about 200
processes.
Just to complete the sintomns.
To access the application, I need to logon in the application. This logon,
stablish a connection to SQL SErver and enable the interface to work.
When I let the connection idle for a little period of time (more or less - 5
minutes), I need to logon on the application again.
Anybody knows what's going on? Are there any settings to change this time-out
configuration just for a specific connections?
Thanks
Best Regards
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200709/1Hi
Does this occur for other applications on this server?
Have you changed anything on the client, other than the server name in the
connection string?
Have you tried other protocols?
Does this occur if the application is running on the server itself?
Are you using a connection pooling?
Do you have AV or ISD software running on the server?
Have you tried connecting a client into the same same hub as the server?
John
"julianohorta via SQLMonster.com" wrote:
> Hello, All!
> Good Afternoon!
> I'm having a strange situation in my SQL SErver 2000 SP3a with 4 Processors,
> 4GB of RAM and high-end disk sub-system.
> I migrate a specific database from another instance with SQL SErver 2000 SP3a
> too to this new server with more hardware resource than another one.
> The application that access this DataBase stablish a connection with SQL
> SErver using TCP/IP, everything works fine. So, if I let the connection
> "sleeping", or better, if I let the connection idle for amount of time, I
> need to stablish the connection to ther SQL SErver again.
> I hadn't the same situation in the old instance as I having. I think that
> it's happening because the other instance was dedicated to this application
> and that new Instance don't.
> In this new Instance I have many other connections simultaneously, about 200
> processes.
> Just to complete the sintomns.
> To access the application, I need to logon in the application. This logon,
> stablish a connection to SQL SErver and enable the interface to work.
> When I let the connection idle for a little period of time (more or less - 5
> minutes), I need to logon on the application again.
>
> Anybody knows what's going on? Are there any settings to change this time-out
> configuration just for a specific connections?
> Thanks
> Best Regards
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200709/1
>
Good Afternoon!
I'm having a strange situation in my SQL SErver 2000 SP3a with 4 Processors,
4GB of RAM and high-end disk sub-system.
I migrate a specific database from another instance with SQL SErver 2000 SP3a
too to this new server with more hardware resource than another one.
The application that access this DataBase stablish a connection with SQL
SErver using TCP/IP, everything works fine. So, if I let the connection
"sleeping", or better, if I let the connection idle for amount of time, I
need to stablish the connection to ther SQL SErver again.
I hadn't the same situation in the old instance as I having. I think that
it's happening because the other instance was dedicated to this application
and that new Instance don't.
In this new Instance I have many other connections simultaneously, about 200
processes.
Just to complete the sintomns.
To access the application, I need to logon in the application. This logon,
stablish a connection to SQL SErver and enable the interface to work.
When I let the connection idle for a little period of time (more or less - 5
minutes), I need to logon on the application again.
Anybody knows what's going on? Are there any settings to change this time-out
configuration just for a specific connections?
Thanks
Best Regards
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200709/1Hi
Does this occur for other applications on this server?
Have you changed anything on the client, other than the server name in the
connection string?
Have you tried other protocols?
Does this occur if the application is running on the server itself?
Are you using a connection pooling?
Do you have AV or ISD software running on the server?
Have you tried connecting a client into the same same hub as the server?
John
"julianohorta via SQLMonster.com" wrote:
> Hello, All!
> Good Afternoon!
> I'm having a strange situation in my SQL SErver 2000 SP3a with 4 Processors,
> 4GB of RAM and high-end disk sub-system.
> I migrate a specific database from another instance with SQL SErver 2000 SP3a
> too to this new server with more hardware resource than another one.
> The application that access this DataBase stablish a connection with SQL
> SErver using TCP/IP, everything works fine. So, if I let the connection
> "sleeping", or better, if I let the connection idle for amount of time, I
> need to stablish the connection to ther SQL SErver again.
> I hadn't the same situation in the old instance as I having. I think that
> it's happening because the other instance was dedicated to this application
> and that new Instance don't.
> In this new Instance I have many other connections simultaneously, about 200
> processes.
> Just to complete the sintomns.
> To access the application, I need to logon in the application. This logon,
> stablish a connection to SQL SErver and enable the interface to work.
> When I let the connection idle for a little period of time (more or less - 5
> minutes), I need to logon on the application again.
>
> Anybody knows what's going on? Are there any settings to change this time-out
> configuration just for a specific connections?
> Thanks
> Best Regards
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200709/1
>
Connections through a server alias, IP address, or any other alternate name are not supported.
Hi
I am trying to connect to another sql server in my company using the IP address for exmp. : 111.111.1.1\SQL2005 but it show this message:
Connections through a server alias, IP address, or any other alternate name are not supported. it was working well on SQL2000
Please help
Have you tried to create an alias in SQL server configuration manager?
Gary
|||Yes I did and is still not accepting|||Hi Ziad,
Can you explain what you did exactly ? did you create the following:
1-create alisan name : mysecondserver
2-port: by default empty , you need to specify the port in case you have firewall issue.
3-protocol: TCP/IP or other..
4-server: IP\instance_name
NB: to be sure about server name on the second server select @.@.servername in query window on the second server.
If you still cannot connect , please send me a direct email, you can find it on my site and i will try to discuss it with you.
Tarek Ghazali
SQL Server MVP
http://www.sqlmvp.com
connections remote SQLExpress
how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>sqlsql
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>sqlsql
connections remote SQLExpress
how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
....
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
......
...
thanks
You need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>
|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>
does not work.
error:
....
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
......
...
thanks
You need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>
|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>
connections remote SQLExpress
how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>
connections remote SQLExpress
how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
....
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
......
...
thanks
You need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>
|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>
does not work.
error:
....
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
......
...
thanks
You need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>
|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>
connections remote SQLExpress
how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
--
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but
>> it does not work.
>>
>> error:
>> ...
>> When connecting to SQL server 2005m this failure may be caused by the
>> fact the under the default settings SQL server does not allow remote
>> connections (provider SQL Network Interfaces, error 26 error, locating
>> server/instance specified).
>> .....
>> ...
>> thanks
>
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
--
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but
>> it does not work.
>>
>> error:
>> ...
>> When connecting to SQL server 2005m this failure may be caused by the
>> fact the under the default settings SQL server does not allow remote
>> connections (provider SQL Network Interfaces, error 26 error, locating
>> server/instance specified).
>> .....
>> ...
>> thanks
>
Subscribe to:
Posts (Atom)