|
Home > Archive > MS SQL Server > October 2006 > Redirecting to a different SQL server on startup: Is it possible?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Redirecting to a different SQL server on startup: Is it possible?
|
|
| mracuraintegra@gmail.com 2006-10-24, 6:29 pm |
| Hey everyone!
I have two SQL 2000 servers set up on two 2K3 machines that people
login to through Terminal Services. My SQL database on Server #1 is my
"primary" one that houses the databases that interfaces with some
applications I wrote. I want to be able to have my apps on Server #2
use the database on Server #1.
If I open the SQL Server Service Manager on Server #2, it sees Server
#1 and I can select it from the dropdown and the apps will use that
database - however, I'd like for it to do this automatically, as each
time someone logs in to Server #2, their service manager points to
Server #1 automatically - I don't like giving access to the SQL Server
Service Manager to users, and besides that, I doubt that they'd
remember to make the switch. Is there any way to configure or automate
this?
P.S. - Yeah, I probably could use replication, but I'm not too familiar
with it, and it kinda looks like it has a lot of overhead in the mode I
need, as I cannot afford to have anyone working with non-synchronized
data.
Thanks!
| |
| Tracy McKibben 2006-10-24, 6:29 pm |
| mracuraintegra@gmail
.com wrote:
> Hey everyone!
>
> I have two SQL 2000 servers set up on two 2K3 machines that people
> login to through Terminal Services. My SQL database on Server #1 is my
> "primary" one that houses the databases that interfaces with some
> applications I wrote. I want to be able to have my apps on Server #2
> use the database on Server #1.
>
> If I open the SQL Server Service Manager on Server #2, it sees Server
> #1 and I can select it from the dropdown and the apps will use that
> database - however, I'd like for it to do this automatically, as each
> time someone logs in to Server #2, their service manager points to
> Server #1 automatically - I don't like giving access to the SQL Server
> Service Manager to users, and besides that, I doubt that they'd
> remember to make the switch. Is there any way to configure or automate
> this?
>
> P.S. - Yeah, I probably could use replication, but I'm not too familiar
> with it, and it kinda looks like it has a lot of overhead in the mode I
> need, as I cannot afford to have anyone working with non-synchronized
> data.
>
> Thanks!
>
What sort of "applications" have you written? Typically, when you write
an application that connects to SQL Server, you have a connection string
defined somewhere that points to the desired database. You can point
the application to a different database by modifying that connection string.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com
| |
| Tibor Karaszi 2006-10-24, 6:29 pm |
| I've been reading your post several times now and I just cannot make sense of it...
The Service Manager is just a tool with which you start and stop the SQL Server service. Why would
some user need to access this tool, isn't the SQL Server service started on the server machine all
the time?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/
< mracuraintegra@gmail
.com> wrote in message
news:1158590562.000979.246670@d34g2000cwd.googlegroups.com...
> Hey everyone!
>
> I have two SQL 2000 servers set up on two 2K3 machines that people
> login to through Terminal Services. My SQL database on Server #1 is my
> "primary" one that houses the databases that interfaces with some
> applications I wrote. I want to be able to have my apps on Server #2
> use the database on Server #1.
>
> If I open the SQL Server Service Manager on Server #2, it sees Server
> #1 and I can select it from the dropdown and the apps will use that
> database - however, I'd like for it to do this automatically, as each
> time someone logs in to Server #2, their service manager points to
> Server #1 automatically - I don't like giving access to the SQL Server
> Service Manager to users, and besides that, I doubt that they'd
> remember to make the switch. Is there any way to configure or automate
> this?
>
> P.S. - Yeah, I probably could use replication, but I'm not too familiar
> with it, and it kinda looks like it has a lot of overhead in the mode I
> need, as I cannot afford to have anyone working with non-synchronized
> data.
>
> Thanks!
>
|
|
|
|
|