MSDE 2000 vs SQL express 2005 ??

Dear all,
We are starting a new developmement of our supervisiob system that will run
uner vista and we will use VS 2005 as a development platform ..
Based on that we need to select proper local database for our local data
archiving.
For that I will certainly us SQL express advance feature edition but some
say that there are connection limitation ?
As far as Icould read around, the only limitation there is is the 4GB
database sizte, 1 single processore handling, and 1GB of RAm for cachin
querries.
I did not get answer that sql express as a limitation in connection, is
there ?
Next I have heard also as an SQL personnal edition version.. Is it the MSDE
base on 2000 ? if its the case then it is not supported under Vista, si my
choice will be explain clearly then..
Thnaks for clarification and comments .
Regards
Serge
MCAD.NET
Thanks andrea, its clear now
"Andrea Montanari" wrote:

> hi Serge,
> calderara wrote:
> then you can only go for SQLExpress sp2 (not yet released)..
>
> tere aren't.. SQLExpress (as MSDE as well) does not include a component to
> limit connections.. it is limited as you already noticed..
> nope
>
> SQL Server Personal edition is based on SQL Server 2000 code base..
> regards
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||Hello,
Perhaps you should also look "out-of-the-box" and take a look at some other
free database systems that do not impose these ridiculous limits such as
1cpu and no SQL Agent.
Primarily, PostgreSQL and Firebird.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:49AE1207-0D8F-4166-8B8E-7FF970F39212@.microsoft.com...[vbcol=seagreen]
> Thanks andrea, its clear now
> "Andrea Montanari" wrote:

MSDE 2000 SP3 Merge Module does not installing on windowx XP

Dear Sirs.
MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
Service Pack.
It is work if SP1 is instaled on Windows XP. But how i can use that merge
modules if SP1 is not installed on Windows XP ?
Thank you in advance.
Install SP1 on Windows XP. You can generally do this if it's a legal copy.
"Irakli Lomidze" <Irakli_Lomidze@.access.sanet.ge> wrote in message
news:uzsiaVNuEHA.2196@.TK2MSFTNGP14.phx.gbl...
> Dear Sirs.
> MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
> Service Pack.
> It is work if SP1 is instaled on Windows XP. But how i can use that merge
> modules if SP1 is not installed on Windows XP ?
> Thank you in advance.
>

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

Dear Experts,
I have downloaded MSDE 2000RelA and i installed it. But where is the
Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would be
greatly appreciated
Thanks
Manish
Three Cheers to Technet for the Help!
Hi,
MSDE will not come with Enterprise manager or Query analyser. You have to
use the command prompt utilizty OSQL to execute all
the TSQL commands. See the details of OSQL utility in books online.
You could also download and use the WEB data ADMIN free tool from microsoft
site.
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Hari
SQL Server MVP
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:42FB064A-B6B7-4F20-A3D4-C437096682E1@.microsoft.com...
> Dear Experts,
> I have downloaded MSDE 2000RelA and i installed it. But where is the
> Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would
> be
> greatly appreciated
> Thanks
> Manish
> --
> Three Cheers to Technet for the Help!

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

Dear Experts,
I have downloaded MSDE 2000RelA and i installed it. But where is the
Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would be
greatly appreciated
Thanks
Manish
--
Three Cheers to Technet for the Help!Hi,
MSDE will not come with Enterprise manager or Query analyser. You have to
use the command prompt utilizty OSQL to execute all
the TSQL commands. See the details of OSQL utility in books online.
You could also download and use the WEB data ADMIN free tool from microsoft
site.
http://www.microsoft.com/downloads/details.aspx?FamilyId=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en
Thanks
Hari
SQL Server MVP
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:42FB064A-B6B7-4F20-A3D4-C437096682E1@.microsoft.com...
> Dear Experts,
> I have downloaded MSDE 2000RelA and i installed it. But where is the
> Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would
> be
> greatly appreciated
> Thanks
> Manish
> --
> Three Cheers to Technet for the Help!|||Thanks Hari
--
Three Cheers to Technet for the Help!
"Hari Prasad" wrote:
> Hi,
> MSDE will not come with Enterprise manager or Query analyser. You have to
> use the command prompt utilizty OSQL to execute all
> the TSQL commands. See the details of OSQL utility in books online.
> You could also download and use the WEB data ADMIN free tool from microsoft
> site.
> http://www.microsoft.com/downloads/details.aspx?FamilyId=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en
> Thanks
> Hari
> SQL Server MVP
>
> "Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
> message news:42FB064A-B6B7-4F20-A3D4-C437096682E1@.microsoft.com...
> > Dear Experts,
> > I have downloaded MSDE 2000RelA and i installed it. But where is the
> > Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would
> > be
> > greatly appreciated
> >
> > Thanks
> > Manish
> > --
> > Three Cheers to Technet for the Help!
>
>

MSDE 2000 Downloaded and Installed But where is Enterprise Manager

Dear Experts,
I have downloaded MSDE 2000RelA and i installed it. But where is the
Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would be
greatly appreciated
Thanks
Manish
--
Three Cheers to technet for the Help!Hi,
MSDE will not come with Enterprise manager or Query analyser. You have to
use the command prompt utilizty OSQL to execute all
the TSQL commands. See the details of OSQL utility in books online.
You could also download and use the WEB data ADMIN free tool from microsoft
site.
http://www.microsoft.com/downloads/...&displaylang=en
Thanks
Hari
SQL Server MVP
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:42FB064A-B6B7-4F20-A3D4-C437096682E1@.microsoft.com...
> Dear Experts,
> I have downloaded MSDE 2000RelA and i installed it. But where is the
> Enterprise Manager and Query Analyzer a-la SQL Server 7.0? Any help would
> be
> greatly appreciated
> Thanks
> Manish
> --
> Three Cheers to technet for the Help!

MSDE / SQL - SERVER

Dear all,
I have installed both environments on my system, running windows 2000.
When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
containing two branches:
- (local) (windows nt) which contains the msde
- named instance which contains the sql server 2000
I have an application running in which I can make a selection between
servers. After installing sql server the servers running on my system are no
longer presented. My application still runs with the msde server if I type in
the name of the server but not with the sql server.
To check wehther the problem is caused by the application or not, I tried to
create a DSN (odbc data source) on my system. Because there the server is
also requested. When I click on the list box for the server no servers are
presented. When I type in the name I get an error message that the connection
failed.
sql server error: 1231
.....
sqlstate: '08001'
sql server error: 17
[microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
access denied
Because I did not see the servers available in the list box I the server
does not exist part of the message seems to match my problem. But looking
into the enterprise manager I have it up and running.
Has someone experienced this in the past and solved it. Can you share the
solution for this problem.
regards,
Danny Gaethofs
Dear all,
I have to rephrase my problem statement. After a bit of experimenting I am
able to get connected to both msde and sql server using my application.
However the problem I described that the servers are not shown in the list
box that opens for example when you create a data source remains.
Because this is a bit crucial when creating new connections can someone help
me out with this and explain why it is happening.
regards,
Danny Gaethofs
"Danny Gaethofs" wrote:

> Dear all,
> I have installed both environments on my system, running windows 2000.
> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
> containing two branches:
> - (local) (windows nt) which contains the msde
> - named instance which contains the sql server 2000
> I have an application running in which I can make a selection between
> servers. After installing sql server the servers running on my system are no
> longer presented. My application still runs with the msde server if I type in
> the name of the server but not with the sql server.
> To check wehther the problem is caused by the application or not, I tried to
> create a DSN (odbc data source) on my system. Because there the server is
> also requested. When I click on the list box for the server no servers are
> presented. When I type in the name I get an error message that the connection
> failed.
> sql server error: 1231
> ....
> sqlstate: '08001'
> sql server error: 17
> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
> access denied
> Because I did not see the servers available in the list box I the server
> does not exist part of the message seems to match my problem. But looking
> into the enterprise manager I have it up and running.
> Has someone experienced this in the past and solved it. Can you share the
> solution for this problem.
> regards,
> Danny Gaethofs
|||When you say "list box," what object are you referring to? I am assuming
this is the developement configuration. How will the architecture look when
you roll this out to your clients? Will they also have two SQL Server
installations on their workstations? Or, will there be an actual server and
then a local MSDE? Or, might there just be several server installations?
You can use the Client Configuration Utility to simulate the "names" of your
production servers but redirect them to each of the "instances" running in
your developement environment.
First, all SQL Server installations run as an "instance." There is the
default instance and up to 15 named instances on any given host. Or, you
can have 16 named instances. They all comprise the <host name>[\<instance
name>], with the default instance being NULL for the instance name. You can
map those, with the Client Configuration Utility, to just a virtual host
name if you wish.
If multiple instances are running on one server, then they can not all share
the same default 1433 port. The other instances can be configured for
specific ports or can be dynamically generated each time the instance is
restarted. If dynamic, then all of your users will have to be on the same
VLAN, the UDP 1434 port must not be blocked, and they must set their client
configuration to Dynamic Discovery for the port detection.
Hope this narrows down this list of issues for you.
Sincerely,
Anthony Thomas

"Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in message
news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
Dear all,
I have to rephrase my problem statement. After a bit of experimenting I am
able to get connected to both msde and sql server using my application.
However the problem I described that the servers are not shown in the list
box that opens for example when you create a data source remains.
Because this is a bit crucial when creating new connections can someone help
me out with this and explain why it is happening.
regards,
Danny Gaethofs
"Danny Gaethofs" wrote:

> Dear all,
> I have installed both environments on my system, running windows 2000.
> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
> containing two branches:
> - (local) (windows nt) which contains the msde
> - named instance which contains the sql server 2000
> I have an application running in which I can make a selection between
> servers. After installing sql server the servers running on my system are
no
> longer presented. My application still runs with the msde server if I type
in
> the name of the server but not with the sql server.
> To check wehther the problem is caused by the application or not, I tried
to
> create a DSN (odbc data source) on my system. Because there the server is
> also requested. When I click on the list box for the server no servers are
> presented. When I type in the name I get an error message that the
connection
> failed.
> sql server error: 1231
> ....
> sqlstate: '08001'
> sql server error: 17
> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
> access denied
> Because I did not see the servers available in the list box I the server
> does not exist part of the message seems to match my problem. But looking
> into the enterprise manager I have it up and running.
> Has someone experienced this in the past and solved it. Can you share the
> solution for this problem.
> regards,
> Danny Gaethofs
|||Dear all,
I have removed everything now, both MSDE and SQL Server. I reinstalled MSDE
only and when I try to create a ODBC DSN the system is not showing me the
available server at all.
Is there an explanation for this behavior and how can I solve it.
regards,
Danny
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> schreef in bericht
news:uW3wrS43EHA.2012@.TK2MSFTNGP15.phx.gbl...
> When you say "list box," what object are you referring to? I am assuming
> this is the developement configuration. How will the architecture look
> when
> you roll this out to your clients? Will they also have two SQL Server
> installations on their workstations? Or, will there be an actual server
> and
> then a local MSDE? Or, might there just be several server installations?
> You can use the Client Configuration Utility to simulate the "names" of
> your
> production servers but redirect them to each of the "instances" running in
> your developement environment.
> First, all SQL Server installations run as an "instance." There is the
> default instance and up to 15 named instances on any given host. Or, you
> can have 16 named instances. They all comprise the <host name>[\<instance
> name>], with the default instance being NULL for the instance name. You
> can
> map those, with the Client Configuration Utility, to just a virtual host
> name if you wish.
> If multiple instances are running on one server, then they can not all
> share
> the same default 1433 port. The other instances can be configured for
> specific ports or can be dynamically generated each time the instance is
> restarted. If dynamic, then all of your users will have to be on the same
> VLAN, the UDP 1434 port must not be blocked, and they must set their
> client
> configuration to Dynamic Discovery for the port detection.
> Hope this narrows down this list of issues for you.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in
> message
> news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
> Dear all,
> I have to rephrase my problem statement. After a bit of experimenting I am
> able to get connected to both msde and sql server using my application.
> However the problem I described that the servers are not shown in the list
> box that opens for example when you create a data source remains.
> Because this is a bit crucial when creating new connections can someone
> help
> me out with this and explain why it is happening.
> regards,
> Danny Gaethofs
> "Danny Gaethofs" wrote:
> no
> in
> to
> connection
>
|||When you run the setup on a system that has or has had the server components
installed, in all likelihood, you have also installed the Client
Configuration utility. Once there, ODBC Administrator is limited as far as
its ability to search out installations. Use the Client Config tool to
define these and then ODBC Administrator to define DSN's on top of that. Be
careful though, because then you are likely forcing the overhead of using
ODBC on top OLEDB. That's just another API layer between you and the
database access.
I would consider using Data Links instead of DSN. These use the native
OLEDB API ans server a similar purpose, persisting the connection parameters
on the local machine. One way to create one quickly is to create a NEW TEXT
FILE, then rename it with the .udl extension. It will automatically be
changed to a Data Link file which can be managed by the Data Link
Administrator.
Sincerely,
Anthony Thomas

"Danny Gaethofs" <dangaet@.home.nl> wrote in message
news:OGKwFlP4EHA.2192@.TK2MSFTNGP14.phx.gbl...
Dear all,
I have removed everything now, both MSDE and SQL Server. I reinstalled MSDE
only and when I try to create a ODBC DSN the system is not showing me the
available server at all.
Is there an explanation for this behavior and how can I solve it.
regards,
Danny
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> schreef in bericht
news:uW3wrS43EHA.2012@.TK2MSFTNGP15.phx.gbl...
> When you say "list box," what object are you referring to? I am assuming
> this is the developement configuration. How will the architecture look
> when
> you roll this out to your clients? Will they also have two SQL Server
> installations on their workstations? Or, will there be an actual server
> and
> then a local MSDE? Or, might there just be several server installations?
> You can use the Client Configuration Utility to simulate the "names" of
> your
> production servers but redirect them to each of the "instances" running in
> your developement environment.
> First, all SQL Server installations run as an "instance." There is the
> default instance and up to 15 named instances on any given host. Or, you
> can have 16 named instances. They all comprise the <host name>[\<instance
> name>], with the default instance being NULL for the instance name. You
> can
> map those, with the Client Configuration Utility, to just a virtual host
> name if you wish.
> If multiple instances are running on one server, then they can not all
> share
> the same default 1433 port. The other instances can be configured for
> specific ports or can be dynamically generated each time the instance is
> restarted. If dynamic, then all of your users will have to be on the same
> VLAN, the UDP 1434 port must not be blocked, and they must set their
> client
> configuration to Dynamic Discovery for the port detection.
> Hope this narrows down this list of issues for you.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in
> message
> news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
> Dear all,
> I have to rephrase my problem statement. After a bit of experimenting I am
> able to get connected to both msde and sql server using my application.
> However the problem I described that the servers are not shown in the list
> box that opens for example when you create a data source remains.
> Because this is a bit crucial when creating new connections can someone
> help
> me out with this and explain why it is happening.
> regards,
> Danny Gaethofs
> "Danny Gaethofs" wrote:
> no
> in
> to
> connection
>

MSDE / SQL - SERVER

Dear all,
I have installed both environments on my system, running windows 2000.
When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
containing two branches:
- (local) (windows nt) which contains the msde
- named instance which contains the sql server 2000
I have an application running in which I can make a selection between
servers. After installing sql server the servers running on my system are no
longer presented. My application still runs with the msde server if I type in
the name of the server but not with the sql server.
To check wehther the problem is caused by the application or not, I tried to
create a DSN (odbc data source) on my system. Because there the server is
also requested. When I click on the list box for the server no servers are
presented. When I type in the name I get an error message that the connection
failed.
sql server error: 1231
....
sqlstate: '08001'
sql server error: 17
[microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
access denied
Because I did not see the servers available in the list box I the server
does not exist part of the message seems to match my problem. But looking
into the enterprise manager I have it up and running.
Has someone experienced this in the past and solved it. Can you share the
solution for this problem.
regards,
Danny GaethofsDear all,
I have to rephrase my problem statement. After a bit of experimenting I am
able to get connected to both msde and sql server using my application.
However the problem I described that the servers are not shown in the list
box that opens for example when you create a data source remains.
Because this is a bit crucial when creating new connections can someone help
me out with this and explain why it is happening.
regards,
Danny Gaethofs
"Danny Gaethofs" wrote:
> Dear all,
> I have installed both environments on my system, running windows 2000.
> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
> containing two branches:
> - (local) (windows nt) which contains the msde
> - named instance which contains the sql server 2000
> I have an application running in which I can make a selection between
> servers. After installing sql server the servers running on my system are no
> longer presented. My application still runs with the msde server if I type in
> the name of the server but not with the sql server.
> To check wehther the problem is caused by the application or not, I tried to
> create a DSN (odbc data source) on my system. Because there the server is
> also requested. When I click on the list box for the server no servers are
> presented. When I type in the name I get an error message that the connection
> failed.
> sql server error: 1231
> ....
> sqlstate: '08001'
> sql server error: 17
> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
> access denied
> Because I did not see the servers available in the list box I the server
> does not exist part of the message seems to match my problem. But looking
> into the enterprise manager I have it up and running.
> Has someone experienced this in the past and solved it. Can you share the
> solution for this problem.
> regards,
> Danny Gaethofs|||When you say "list box," what object are you referring to? I am assuming
this is the developement configuration. How will the architecture look when
you roll this out to your clients? Will they also have two SQL Server
installations on their workstations? Or, will there be an actual server and
then a local MSDE? Or, might there just be several server installations?
You can use the Client Configuration Utility to simulate the "names" of your
production servers but redirect them to each of the "instances" running in
your developement environment.
First, all SQL Server installations run as an "instance." There is the
default instance and up to 15 named instances on any given host. Or, you
can have 16 named instances. They all comprise the <host name>[\<instance
name>], with the default instance being NULL for the instance name. You can
map those, with the Client Configuration Utility, to just a virtual host
name if you wish.
If multiple instances are running on one server, then they can not all share
the same default 1433 port. The other instances can be configured for
specific ports or can be dynamically generated each time the instance is
restarted. If dynamic, then all of your users will have to be on the same
VLAN, the UDP 1434 port must not be blocked, and they must set their client
configuration to Dynamic Discovery for the port detection.
Hope this narrows down this list of issues for you.
Sincerely,
Anthony Thomas
"Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in message
news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
Dear all,
I have to rephrase my problem statement. After a bit of experimenting I am
able to get connected to both msde and sql server using my application.
However the problem I described that the servers are not shown in the list
box that opens for example when you create a data source remains.
Because this is a bit crucial when creating new connections can someone help
me out with this and explain why it is happening.
regards,
Danny Gaethofs
"Danny Gaethofs" wrote:
> Dear all,
> I have installed both environments on my system, running windows 2000.
> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
> containing two branches:
> - (local) (windows nt) which contains the msde
> - named instance which contains the sql server 2000
> I have an application running in which I can make a selection between
> servers. After installing sql server the servers running on my system are
no
> longer presented. My application still runs with the msde server if I type
in
> the name of the server but not with the sql server.
> To check wehther the problem is caused by the application or not, I tried
to
> create a DSN (odbc data source) on my system. Because there the server is
> also requested. When I click on the list box for the server no servers are
> presented. When I type in the name I get an error message that the
connection
> failed.
> sql server error: 1231
> ....
> sqlstate: '08001'
> sql server error: 17
> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
> access denied
> Because I did not see the servers available in the list box I the server
> does not exist part of the message seems to match my problem. But looking
> into the enterprise manager I have it up and running.
> Has someone experienced this in the past and solved it. Can you share the
> solution for this problem.
> regards,
> Danny Gaethofs|||Dear all,
I have removed everything now, both MSDE and SQL Server. I reinstalled MSDE
only and when I try to create a ODBC DSN the system is not showing me the
available server at all.
Is there an explanation for this behavior and how can I solve it.
regards,
Danny
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> schreef in bericht
news:uW3wrS43EHA.2012@.TK2MSFTNGP15.phx.gbl...
> When you say "list box," what object are you referring to? I am assuming
> this is the developement configuration. How will the architecture look
> when
> you roll this out to your clients? Will they also have two SQL Server
> installations on their workstations? Or, will there be an actual server
> and
> then a local MSDE? Or, might there just be several server installations?
> You can use the Client Configuration Utility to simulate the "names" of
> your
> production servers but redirect them to each of the "instances" running in
> your developement environment.
> First, all SQL Server installations run as an "instance." There is the
> default instance and up to 15 named instances on any given host. Or, you
> can have 16 named instances. They all comprise the <host name>[\<instance
> name>], with the default instance being NULL for the instance name. You
> can
> map those, with the Client Configuration Utility, to just a virtual host
> name if you wish.
> If multiple instances are running on one server, then they can not all
> share
> the same default 1433 port. The other instances can be configured for
> specific ports or can be dynamically generated each time the instance is
> restarted. If dynamic, then all of your users will have to be on the same
> VLAN, the UDP 1434 port must not be blocked, and they must set their
> client
> configuration to Dynamic Discovery for the port detection.
> Hope this narrows down this list of issues for you.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in
> message
> news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
> Dear all,
> I have to rephrase my problem statement. After a bit of experimenting I am
> able to get connected to both msde and sql server using my application.
> However the problem I described that the servers are not shown in the list
> box that opens for example when you create a data source remains.
> Because this is a bit crucial when creating new connections can someone
> help
> me out with this and explain why it is happening.
> regards,
> Danny Gaethofs
> "Danny Gaethofs" wrote:
>> Dear all,
>> I have installed both environments on my system, running windows 2000.
>> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
>> containing two branches:
>> - (local) (windows nt) which contains the msde
>> - named instance which contains the sql server 2000
>> I have an application running in which I can make a selection between
>> servers. After installing sql server the servers running on my system are
> no
>> longer presented. My application still runs with the msde server if I
>> type
> in
>> the name of the server but not with the sql server.
>> To check wehther the problem is caused by the application or not, I tried
> to
>> create a DSN (odbc data source) on my system. Because there the server is
>> also requested. When I click on the list box for the server no servers
>> are
>> presented. When I type in the name I get an error message that the
> connection
>> failed.
>> sql server error: 1231
>> ....
>> sqlstate: '08001'
>> sql server error: 17
>> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
>> access denied
>> Because I did not see the servers available in the list box I the server
>> does not exist part of the message seems to match my problem. But looking
>> into the enterprise manager I have it up and running.
>> Has someone experienced this in the past and solved it. Can you share the
>> solution for this problem.
>> regards,
>> Danny Gaethofs
>|||When you run the setup on a system that has or has had the server components
installed, in all likelihood, you have also installed the Client
Configuration utility. Once there, ODBC Administrator is limited as far as
its ability to search out installations. Use the Client Config tool to
define these and then ODBC Administrator to define DSN's on top of that. Be
careful though, because then you are likely forcing the overhead of using
ODBC on top OLEDB. That's just another API layer between you and the
database access.
I would consider using Data Links instead of DSN. These use the native
OLEDB API ans server a similar purpose, persisting the connection parameters
on the local machine. One way to create one quickly is to create a NEW TEXT
FILE, then rename it with the .udl extension. It will automatically be
changed to a Data Link file which can be managed by the Data Link
Administrator.
Sincerely,
Anthony Thomas
"Danny Gaethofs" <dangaet@.home.nl> wrote in message
news:OGKwFlP4EHA.2192@.TK2MSFTNGP14.phx.gbl...
Dear all,
I have removed everything now, both MSDE and SQL Server. I reinstalled MSDE
only and when I try to create a ODBC DSN the system is not showing me the
available server at all.
Is there an explanation for this behavior and how can I solve it.
regards,
Danny
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> schreef in bericht
news:uW3wrS43EHA.2012@.TK2MSFTNGP15.phx.gbl...
> When you say "list box," what object are you referring to? I am assuming
> this is the developement configuration. How will the architecture look
> when
> you roll this out to your clients? Will they also have two SQL Server
> installations on their workstations? Or, will there be an actual server
> and
> then a local MSDE? Or, might there just be several server installations?
> You can use the Client Configuration Utility to simulate the "names" of
> your
> production servers but redirect them to each of the "instances" running in
> your developement environment.
> First, all SQL Server installations run as an "instance." There is the
> default instance and up to 15 named instances on any given host. Or, you
> can have 16 named instances. They all comprise the <host name>[\<instance
> name>], with the default instance being NULL for the instance name. You
> can
> map those, with the Client Configuration Utility, to just a virtual host
> name if you wish.
> If multiple instances are running on one server, then they can not all
> share
> the same default 1433 port. The other instances can be configured for
> specific ports or can be dynamically generated each time the instance is
> restarted. If dynamic, then all of your users will have to be on the same
> VLAN, the UDP 1434 port must not be blocked, and they must set their
> client
> configuration to Dynamic Discovery for the port detection.
> Hope this narrows down this list of issues for you.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Danny Gaethofs" <DannyGaethofs@.discussions.microsoft.com> wrote in
> message
> news:85A69D33-EFD8-4D8E-A908-34027B510269@.microsoft.com...
> Dear all,
> I have to rephrase my problem statement. After a bit of experimenting I am
> able to get connected to both msde and sql server using my application.
> However the problem I described that the servers are not shown in the list
> box that opens for example when you create a data source remains.
> Because this is a bit crucial when creating new connections can someone
> help
> me out with this and explain why it is happening.
> regards,
> Danny Gaethofs
> "Danny Gaethofs" wrote:
>> Dear all,
>> I have installed both environments on my system, running windows 2000.
>> When I start the SQL Enterprise Manager I can see 1 SQL Server Group,
>> containing two branches:
>> - (local) (windows nt) which contains the msde
>> - named instance which contains the sql server 2000
>> I have an application running in which I can make a selection between
>> servers. After installing sql server the servers running on my system are
> no
>> longer presented. My application still runs with the msde server if I
>> type
> in
>> the name of the server but not with the sql server.
>> To check wehther the problem is caused by the application or not, I tried
> to
>> create a DSN (odbc data source) on my system. Because there the server is
>> also requested. When I click on the list box for the server no servers
>> are
>> presented. When I type in the name I get an error message that the
> connection
>> failed.
>> sql server error: 1231
>> ....
>> sqlstate: '08001'
>> sql server error: 17
>> [microsoft][odbc sql server dirver][dbnetlib]sql server does not exist or
>> access denied
>> Because I did not see the servers available in the list box I the server
>> does not exist part of the message seems to match my problem. But looking
>> into the enterprise manager I have it up and running.
>> Has someone experienced this in the past and solved it. Can you share the
>> solution for this problem.
>> regards,
>> Danny Gaethofs
>

MSDE

Dear all,
I am trying to connect to MSDE on a remote machine, on my local network
using enterprise manager using SQL authentication, the passwords are
correct as I can log in locally, however on trying to register the
remote SQL MSDE i get the following error message 'SQL Server does not
exist or access denied ConnectionOpen(Connect())'
Help, does anyone know any solutions.
Regards
Stuart
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!You probably have no network protocols enabled on the remote computer.
Try using SVRNETCN.exe on the remote computer to enable network protocols
(TCP/IP, named pipes). SVRNETCN.exe is located in folder 'C:\Program
Files\Microsoft SQL Server\80\Tools\Binn'.
Oskari
Stuart Seeley <sseeley@.btinternet.com> wrote in
news:ODIcdKTCEHA.712@.tk2msftngp13.phx.gbl:

>
> Dear all,
> I am trying to connect to MSDE on a remote machine, on my local network
> using enterprise manager using SQL authentication, the passwords are
> correct as I can log in locally, however on trying to register the
> remote SQL MSDE i get the following error message 'SQL Server does not
> exist or access denied ConnectionOpen(Connect())'
> Help, does anyone know any solutions.
> Regards
> Stuart
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||Thanks, worked a treat, much appreciated
Stuart
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

MSDB database is in SUSPECT status

Dear Sir,
There was a power outage on 19/01/2005.
Since then, MSDB database is in SUSPECT status and an error appeared
(Error No 926)
since the error, we can not backup and/ or restore the database.
PLS advice
Thanks and Regards
Mousbah
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mousbah" <Mousbah@.discussions.microsoft.com> wrote in message
news:EAE81F4B-687B-45B2-9121-18EA2D37A245@.microsoft.com...
> Dear Sir,
> There was a power outage on 19/01/2005.
> Since then, MSDB database is in SUSPECT status and an error appeared
> (Error No 926)
> since the error, we can not backup and/ or restore the database.
> PLS advice
> Thanks and Regards
> Mousbah

MSDB database is in SUSPECT status

Dear Sir,
There was a power outage on 19/01/2005.
Since then, MSDB database is in SUSPECT status and an error appeared
(Error No 926)
since the error, we can not backup and/ or restore the database.
PLS advice
Thanks and Regards
Mousbahhttp://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mousbah" <Mousbah@.discussions.microsoft.com> wrote in message
news:EAE81F4B-687B-45B2-9121-18EA2D37A245@.microsoft.com...
> Dear Sir,
> There was a power outage on 19/01/2005.
> Since then, MSDB database is in SUSPECT status and an error appeared
> (Error No 926)
> since the error, we can not backup and/ or restore the database.
> PLS advice
> Thanks and Regards
> Mousbah

MSDB database is in SUSPECT status

Dear Sir,
There was a power outage on 19/01/2005.
Since then, MSDB database is in SUSPECT status and an error appeared
(Error No 926)
since the error, we can not backup and/ or restore the database.
PLS advice
Thanks and Regards
Mousbahhttp://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Mousbah" <Mousbah@.discussions.microsoft.com> wrote in message
news:EAE81F4B-687B-45B2-9121-18EA2D37A245@.microsoft.com...
> Dear Sir,
> There was a power outage on 19/01/2005.
> Since then, MSDB database is in SUSPECT status and an error appeared
> (Error No 926)
> since the error, we can not backup and/ or restore the database.
> PLS advice
> Thanks and Regards
> Mousbah