Connections & Single-User

Hello all,
As an sql novice I have created some Maintenance Plans which seemed to work
ok except for integrity checks. As I can read from the logs they could'n be
executed because the db had to be in Single-User. Ok got that.
But the problem is that other servers are running some foreground &
background programs that connect to the sql svr. When I closed the
connections on our sql, the other server keeps connecting back resulting in
the fact I couldn't close the connections. This weekend when I rebooted the
other servers they lost connection to sql resulting in 0 connections to the
db.
How can this be done then, if remote servers keep connecting ? Is there a
safe way to get my db's in single user ?
I presume my test by closing the active connections to the sql via Ent. Mgr
was also not a good thing to do?
Rgds,
T.
The way to handle it is to remove the check for the option
to repair errors on your integrity checks in the maintenance
plan. You don't really want automatic repairs happening if
your dbcc checkdbs fail. You would want to intervene
yourself, determine what caused the consistency error, fix
the underlying problem and then take whatever course of
action based on what the underlying problem is.
-Sue
On Mon, 20 Sep 2004 19:21:26 GMT, "TieTo" <nobody@.home.net>
wrote:

>Hello all,
>As an sql novice I have created some Maintenance Plans which seemed to work
>ok except for integrity checks. As I can read from the logs they could'n be
>executed because the db had to be in Single-User. Ok got that.
>But the problem is that other servers are running some foreground &
>background programs that connect to the sql svr. When I closed the
>connections on our sql, the other server keeps connecting back resulting in
>the fact I couldn't close the connections. This weekend when I rebooted the
>other servers they lost connection to sql resulting in 0 connections to the
>db.
>How can this be done then, if remote servers keep connecting ? Is there a
>safe way to get my db's in single user ?
>I presume my test by closing the active connections to the sql via Ent. Mgr
>was also not a good thing to do?
>Rgds,
>T.
>
>
|||"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:4h5vk0l1mvrer6h775b6dgb2slkg5441r0@.4ax.com...
> The way to handle it is to remove the check for the option
> to repair errors on your integrity checks in the maintenance
> plan. You don't really want automatic repairs happening if
> your dbcc checkdbs fail. You would want to intervene
> yourself, determine what caused the consistency error, fix
> the underlying problem and then take whatever course of
> action based on what the underlying problem is.
> -Sue
>
Ok Sue, I will do so. Thank you for your help!!
Rgds,
T.

Connection String Problem

I am working on a new website where the ISP (GoDaddy) has plans that include
a sql server (one db). I setup the db, built and partially populated some
tables and, from an aspx page on that account, I figured out the connection
string - works pretty well (I sure miss EM!). Now, I want to create a
windows application (desktop) to manage some aspects of that database but
the server name that works from the aspx page does not work from a windows
application. The sql server "address" is something like"
xxsql01.prod.xxxx1.secureserver.net
(Not sure if that is a name limited to the account so I "x" out parts of
it?) and there is a DB name which I use as the Initial Catalog.
Has anyone dealt with this type of server before? Any hints on how to
address it externally? I tried prefixing that address with the domain name
of the ISP account but that did not help
Appreciate any suggestions.
WayneUsing Enterprise Manager, I can register SQL Server hosted at my ISP via IP
address. Just try specifying the IP for the server name.
"Wayne Wengert" <wayneDONTWANTSPAM@.wengert.com> wrote in message
news:eW6auhuDFHA.2220@.TK2MSFTNGP09.phx.gbl...
> I am working on a new website where the ISP (GoDaddy) has plans that
include
> a sql server (one db). I setup the db, built and partially populated some
> tables and, from an aspx page on that account, I figured out the
connection
> string - works pretty well (I sure miss EM!). Now, I want to create a
> windows application (desktop) to manage some aspects of that database but
> the server name that works from the aspx page does not work from a windows
> application. The sql server "address" is something like"
> xxsql01.prod.xxxx1.secureserver.net
> (Not sure if that is a name limited to the account so I "x" out parts of
> it?) and there is a DB name which I use as the Initial Catalog.
>
> Has anyone dealt with this type of server before? Any hints on how to
> address it externally? I tried prefixing that address with the domain name
> of the ISP account but that did not help
>
> Appreciate any suggestions.
>
> Wayne
>|||Ask your provider if the SQL-Server is directly accessible from the internet
and not blocked by a firewall. Many (most ?) ISP are now blocking the port
1433 to *protect* the sql-servers from outside attacks.
Even if the SQL-Server is accessible from the outside (Internet), if there
is a proxy then the connection string might be different then the one used
for ASP.NET.
S. L.
"Wayne Wengert" <wayneDONTWANTSPAM@.wengert.com> wrote in message
news:eW6auhuDFHA.2220@.TK2MSFTNGP09.phx.gbl...
>I am working on a new website where the ISP (GoDaddy) has plans that
>include
> a sql server (one db). I setup the db, built and partially populated some
> tables and, from an aspx page on that account, I figured out the
> connection
> string - works pretty well (I sure miss EM!). Now, I want to create a
> windows application (desktop) to manage some aspects of that database but
> the server name that works from the aspx page does not work from a windows
> application. The sql server "address" is something like"
> xxsql01.prod.xxxx1.secureserver.net
> (Not sure if that is a name limited to the account so I "x" out parts of
> it?) and there is a DB name which I use as the Initial Catalog.
>
> Has anyone dealt with this type of server before? Any hints on how to
> address it externally? I tried prefixing that address with the domain name
> of the ISP account but that did not help
>
> Appreciate any suggestions.
>
> Wayne
>|||Thanks guys. I'll pursue those suggestions.
Wayne
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:OqUzD9uDFHA.148@.TK2MSFTNGP14.phx.gbl...
> Ask your provider if the SQL-Server is directly accessible from the
internet
> and not blocked by a firewall. Many (most ?) ISP are now blocking the
port
> 1433 to *protect* the sql-servers from outside attacks.
> Even if the SQL-Server is accessible from the outside (Internet), if there
> is a proxy then the connection string might be different then the one used
> for ASP.NET.
> S. L.
> "Wayne Wengert" <wayneDONTWANTSPAM@.wengert.com> wrote in message
> news:eW6auhuDFHA.2220@.TK2MSFTNGP09.phx.gbl...
some
but
windows
name
>