I am running 2 instances of MSDE2000 on a server with Win2K server SP4 and
ISA Server 2000. From the workstations on the network I am able to create
an ODBC connection to the default instance of SQL (MSSQL) but receive an
error when trying to connect to the 2nd instance (MSSQL\INSTANCENAME). Both
names appear in the dropdown list when creating the ODBC connection. Both
instances are running and networking for TCP/IP is enabled using SVRNETCN.
Both instances use the same SA password and connection is made using SQL
Authentication.
Error Message is
Connection Failed
SQLState 01000
SQL Server Error: 10048
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection Failed
SQLState 08001
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied
If I stop both instances of SQL and start only the 2nd instance i am then
able to connect to it but am unable to connect to the default instance when
it is restarted. It seems that the first instance of SQL to start can have
a connection made to it and any other instances cannot have an ODBC
connection. I think it may be related to ISA Server but cannot confirm at
this stage
Any advice would be appreciated.
Darrin
Darrin Acreman wrote:
> I am running 2 instances of MSDE2000 on a server with Win2K server SP4 and
> ISA Server 2000. From the workstations on the network I am able to create
> an ODBC connection to the default instance of SQL (MSSQL) but receive an
> error when trying to connect to the 2nd instance (MSSQL\INSTANCENAME). Both
> names appear in the dropdown list when creating the ODBC connection. Both
> instances are running and networking for TCP/IP is enabled using SVRNETCN.
> Both instances use the same SA password and connection is made using SQL
> Authentication.
> Error Message is
> Connection Failed
> SQLState 01000
> SQL Server Error: 10048
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
> Connection Failed
> SQLState 08001
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied
> If I stop both instances of SQL and start only the 2nd instance i am then
> able to connect to it but am unable to connect to the default instance when
> it is restarted. It seems that the first instance of SQL to start can have
> a connection made to it and any other instances cannot have an ODBC
> connection. I think it may be related to ISA Server but cannot confirm at
> this stage
> Any advice would be appreciated.
> Darrin
>
Check the port numbers for both instances, they should be different
different. Check the application log/system log for any errors generated
by the second instance you start.
Showing posts with label instances. Show all posts
Showing posts with label instances. Show all posts
Friday, March 30, 2012
MSDE and Full SQL Server
This might be a stupid questions but,
Can you have a MSDE 2000 and SQL server
standard/enterprise on the same machine?
If not, can you have to instances of SQL databse with
different passwords for the 'sa' account in the respective
instances.
Many thanks
NicYou can have up to 16 instances of any edition of SQL Server 2000 (including
MSDE 2000) on a single computer.
sa is just one login that can be a member of the sysadmin fixed server role.
Any login in the sysadmin fixed server role has sys admin priviledges for
that instance of SQL Server. This would extend to any database for the
instance.
Alan Brewer [MSFT]
Lead programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rightssql
Can you have a MSDE 2000 and SQL server
standard/enterprise on the same machine?
If not, can you have to instances of SQL databse with
different passwords for the 'sa' account in the respective
instances.
Many thanks
NicYou can have up to 16 instances of any edition of SQL Server 2000 (including
MSDE 2000) on a single computer.
sa is just one login that can be a member of the sysadmin fixed server role.
Any login in the sysadmin fixed server role has sys admin priviledges for
that instance of SQL Server. This would extend to any database for the
instance.
Alan Brewer [MSFT]
Lead programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rightssql
MSDE and Computer Name Change
Hi!
I know that the default instance of MSDE is the computer name. If the
computer's name is subsequently changed, will the default instance’s name
change to the new computer name as well.
Thanks for your thoughts.
Actually the default instance name is not the computer name. All instances
are addressed in connections strings as <computer name>\<instance name>. If
you leave off the instance name then SQL Server assumes you are talking
about the default instance. So yes, if you change the computer name, all
your connection strings will break, probably including some that you aren't
aware of so changing the computer name is a risky thing to do. At a minimum
you will nee to use sp_addserver and restart MSDE to change SQL Server's
local server name.
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
"Gene" <Gene@.discussions.microsoft.com> wrote in message
news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
> Hi!
> I know that the default instance of MSDE is the computer name. If the
> computer's name is subsequently changed, will the default instance's name
> change to the new computer name as well.
> Thanks for your thoughts.
|||Thanks for the input Roger. I don't know much about SQL, but my guess would
have been pretty close to your response. I'm concerned about breaking
something I'm not aware of and not knowing where to go from there.
Regards,
Gene
"Roger Wolter[MSFT]" wrote:
> Actually the default instance name is not the computer name. All instances
> are addressed in connections strings as <computer name>\<instance name>. If
> you leave off the instance name then SQL Server assumes you are talking
> about the default instance. So yes, if you change the computer name, all
> your connection strings will break, probably including some that you aren't
> aware of so changing the computer name is a risky thing to do. At a minimum
> you will nee to use sp_addserver and restart MSDE to change SQL Server's
> local server name.
> --
> 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
> "Gene" <Gene@.discussions.microsoft.com> wrote in message
> news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
>
>
sql
I know that the default instance of MSDE is the computer name. If the
computer's name is subsequently changed, will the default instance’s name
change to the new computer name as well.
Thanks for your thoughts.
Actually the default instance name is not the computer name. All instances
are addressed in connections strings as <computer name>\<instance name>. If
you leave off the instance name then SQL Server assumes you are talking
about the default instance. So yes, if you change the computer name, all
your connection strings will break, probably including some that you aren't
aware of so changing the computer name is a risky thing to do. At a minimum
you will nee to use sp_addserver and restart MSDE to change SQL Server's
local server name.
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
"Gene" <Gene@.discussions.microsoft.com> wrote in message
news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
> Hi!
> I know that the default instance of MSDE is the computer name. If the
> computer's name is subsequently changed, will the default instance's name
> change to the new computer name as well.
> Thanks for your thoughts.
|||Thanks for the input Roger. I don't know much about SQL, but my guess would
have been pretty close to your response. I'm concerned about breaking
something I'm not aware of and not knowing where to go from there.
Regards,
Gene
"Roger Wolter[MSFT]" wrote:
> Actually the default instance name is not the computer name. All instances
> are addressed in connections strings as <computer name>\<instance name>. If
> you leave off the instance name then SQL Server assumes you are talking
> about the default instance. So yes, if you change the computer name, all
> your connection strings will break, probably including some that you aren't
> aware of so changing the computer name is a risky thing to do. At a minimum
> you will nee to use sp_addserver and restart MSDE to change SQL Server's
> local server name.
> --
> 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
> "Gene" <Gene@.discussions.microsoft.com> wrote in message
> news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
>
>
sql
Wednesday, March 28, 2012
MSDE 2K Merge replication without network
I'm new to replication, but have a challenging requirement...
I have multiple MSDE 2K instances that will be used by a surveying crew that
may be distributed across many miles - sometimes in jungle or desert
environments where they never even see each other.
All/any data in any instance is updateable; all changes must be propagated -
at irregular intervals (daily or?) to all other instances. There is no
designated "master" (or perhaps all instances could be considered "masters").
We can live with a hub-and-spoke replication topology (ie, all replication
occurs via a hub instance at the field camp, which then, eventually,
replicates to all the other spokes).
===> The instances are NOT (and are NEVER) connected over a network! (not
even wireless - although we should be able to at least keep the system clocks
synchronized, if that's required for reliable synchronization, by having
each system have a GPS receiver).
Therefore, all synchronization must be via files (flash drive, etc). Even
the definition/setup of the synchronization (subscriptions) must not require
a network connection.
Can Merge replication be implemented between MSDE instances, given these
network constraints?
Thanks!
David
Unless you provide at least an occasional network connectivity between
publisher and subscribers merge replication cannot be implemented.
Yury
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
> that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
> propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
> "masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
> clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
> require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
|||its probably better to use transactional replication with a local dummy
subscriber. Collect the contents of msrepl_commands and then mail them back
and forth. This will be a list of all database activity which you can run on
each node for synchronization purposes.
Hilary Cotter
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
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
"masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
I have multiple MSDE 2K instances that will be used by a surveying crew that
may be distributed across many miles - sometimes in jungle or desert
environments where they never even see each other.
All/any data in any instance is updateable; all changes must be propagated -
at irregular intervals (daily or?) to all other instances. There is no
designated "master" (or perhaps all instances could be considered "masters").
We can live with a hub-and-spoke replication topology (ie, all replication
occurs via a hub instance at the field camp, which then, eventually,
replicates to all the other spokes).
===> The instances are NOT (and are NEVER) connected over a network! (not
even wireless - although we should be able to at least keep the system clocks
synchronized, if that's required for reliable synchronization, by having
each system have a GPS receiver).
Therefore, all synchronization must be via files (flash drive, etc). Even
the definition/setup of the synchronization (subscriptions) must not require
a network connection.
Can Merge replication be implemented between MSDE instances, given these
network constraints?
Thanks!
David
Unless you provide at least an occasional network connectivity between
publisher and subscribers merge replication cannot be implemented.
Yury
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
> that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
> propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
> "masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
> clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
> require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
|||its probably better to use transactional replication with a local dummy
subscriber. Collect the contents of msrepl_commands and then mail them back
and forth. This will be a list of all database activity which you can run on
each node for synchronization purposes.
Hilary Cotter
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
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
"masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
Monday, March 19, 2012
MSDE -> Express Upgrade problem.
Hello!
I'm trying to upgrade old MSDE instances to SQL Server 2005 Express SP1.
The following command fails:
SQLEXPR.EXE /qb UPGRADE=SQL_Engine INSTANCENAME=XXX ADDLOCAL=Client_Components,Connectivity
because the domain\x user cannot login. We have disabled Windows authentication. Is there a way to supply the SA login instead of a domain user?
Problem no #2:
After upgrading with Windows Authentication turned on, current SQL users cannot login (sa). Is Mixed authentication mode turned off during upgrade? Or what else could be the problem?
Our application is distributed around Europe. We have no control over our customers security settings/logins.
Also, the database contains sensitive data. Giving Windows Administrators access to the database is out of the question.
Kind regards
A
Check in the template.ini file that's in the high-level directory of the install media; the options are explained pretty well in there but in brief you can specify accounts, passwords, and security mode.Wednesday, March 7, 2012
MSDE
Hi there,
I have a couple of questions related to MSDE 2000.
1. Is there only one SA account for all instances that may be present on a system or each instance has its own SA account and password?
2. When there is an MSDE instance already installed and it is set to Windows Authentication mode, are the instances installed later going to have to use Windows Authentication mode or they could be in Mixed mode?
Thank you for your help,
GDD1499
GDD1499,
Each instance of MSDE 2000 is completely independent and separate from all
other instances. So, to be specific, each instance of MSDE 2000 has its own
sa account and password. Additionally, one (or more) instances of MSDE 2000
can use Windows Authentication mode, while other instances on the same box
may be using Mixed Mode Authentication.
Chief Tenaya
"GDD1499" <anonymous@.discussions.microsoft.com> wrote in message
news:A38DA9C9-13F4-4C67-B911-74F24CD9D9DF@.microsoft.com...
> Hi there,
> I have a couple of questions related to MSDE 2000.
> 1. Is there only one SA account for all instances that may be present on a
system or each instance has its own SA account and password?
> 2. When there is an MSDE instance already installed and it is set to
Windows Authentication mode, are the instances installed later going to have
to use Windows Authentication mode or they could be in Mixed mode?
> Thank you for your help,
> GDD1499
I have a couple of questions related to MSDE 2000.
1. Is there only one SA account for all instances that may be present on a system or each instance has its own SA account and password?
2. When there is an MSDE instance already installed and it is set to Windows Authentication mode, are the instances installed later going to have to use Windows Authentication mode or they could be in Mixed mode?
Thank you for your help,
GDD1499
GDD1499,
Each instance of MSDE 2000 is completely independent and separate from all
other instances. So, to be specific, each instance of MSDE 2000 has its own
sa account and password. Additionally, one (or more) instances of MSDE 2000
can use Windows Authentication mode, while other instances on the same box
may be using Mixed Mode Authentication.
Chief Tenaya
"GDD1499" <anonymous@.discussions.microsoft.com> wrote in message
news:A38DA9C9-13F4-4C67-B911-74F24CD9D9DF@.microsoft.com...
> Hi there,
> I have a couple of questions related to MSDE 2000.
> 1. Is there only one SA account for all instances that may be present on a
system or each instance has its own SA account and password?
> 2. When there is an MSDE instance already installed and it is set to
Windows Authentication mode, are the instances installed later going to have
to use Windows Authentication mode or they could be in Mixed mode?
> Thank you for your help,
> GDD1499
Subscribe to:
Posts (Atom)