Hi,
I have local MSDE installed on my laptop. When I am physically
connected to our network I can connect through my ODBC application
without issue.
However, when I have wireless networking enabled the first time I try to
connect I get a timeout. But, I'm able to immediately connect after
that initial timeout without a problem. This only occurs when wireless
networking is enabled, as the timeout does not occur with a physical LAN
connection.
I have the following installation:
MDAC SDK 2.8
MSDE 8.00.761
XP SP2
VS.NET 7.1
Any help would be greatly appreciated.
Thanks,
John
I am having a similar issue using SQL querries over a wireless connection.
Is there a technology that is better suited for wireless? Say .net?
Thanks in advance...
"JohnD" wrote:
> Hi,
> I have local MSDE installed on my laptop. When I am physically
> connected to our network I can connect through my ODBC application
> without issue.
> However, when I have wireless networking enabled the first time I try to
> connect I get a timeout. But, I'm able to immediately connect after
> that initial timeout without a problem. This only occurs when wireless
> networking is enabled, as the timeout does not occur with a physical LAN
> connection.
> I have the following installation:
> MDAC SDK 2.8
> MSDE 8.00.761
> XP SP2
> VS.NET 7.1
> Any help would be greatly appreciated.
> Thanks,
> John
>
|||Do you have the same problem if you use an IP address instead of the MSDE
instance name? Perhaps you're having a name resolution problem?
Jim
"Chris James" <Chris James@.discussions.microsoft.com> wrote in message
news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...[vbcol=seagreen]
>I am having a similar issue using SQL querries over a wireless connection.
> Is there a technology that is better suited for wireless? Say .net?
> Thanks in advance...
> "JohnD" wrote:
|||Thanks for the post Jim, Ive tried it using IP and Instance name... The
funny thing is that not all wireless installations have this issue, I have
two sites across the street and down about 1/4 mile. One site with approx
250' between wireless access point and client work fairly reliably, the other
is only 50' apart and they fail all the time. I wonder if its the
application making too many querries and boging down the wireless. Both
sites are using identical equipment as well.
"Jim Young" wrote:
> Do you have the same problem if you use an IP address instead of the MSDE
> instance name? Perhaps you're having a name resolution problem?
> Jim
> "Chris James" <Chris James@.discussions.microsoft.com> wrote in message
> news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...
>
>
Showing posts with label network. Show all posts
Showing posts with label network. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MSDE SP3a and XP SP2 on Localhost
I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:
> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:
> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:
> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:
> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql
MSDE sharing on peer-to-peer network
We have a Front End/Back End database. The Back End is stored in a shared
folder on a per-to-peer network.
1. Can we use MSDE to back-end the database and have up to five users access
it from each of their workstations if we change the front-end to an Access
project using ADO?
2. If this can be done how will the performance compare? There are up to 40
tables containing up to 150MB of data.
Thanks
Terry
hi Terry,
Terry wrote:
> We have a Front End/Back End database. The Back End is stored in a
> shared folder on a per-to-peer network.
> 1. Can we use MSDE to back-end the database and have up to five users
> access it from each of their workstations if we change the front-end
> to an Access project using ADO?
you should not store SQL Server/MSDE databases in a network share, nor
should they be on a remote one..
users only needs to access MSDE, and thus data throught it's service and do
not need physical access to the database os files, both for security reasons
and technical perspective...
regarding Access/ADO, you actually do not need this path as you could go
with other model (c#/ADO.Net or whatever), but it's ok..
> 2. If this can be done how will the performance compare? There are up
> to 40 tables containing up to 150MB of data.
it dependes on your code quality and logic... avoid SELECT * FROM
myMillionTable and follow standard code quality and best practice for
database applications
you have to test your scenario...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello Andrea
Thanks for the information.
I think I worded the question badly in terms of sharing - I understand where
you are coming from (I think). Can a user on, say Workstation 2 access the
data in an MSDE database on Workstation 1?
Terry
=================================
"Andrea Montanari" wrote:
> hi Terry,
> Terry wrote:
> you should not store SQL Server/MSDE databases in a network share, nor
> should they be on a remote one..
> users only needs to access MSDE, and thus data throught it's service and do
> not need physical access to the database os files, both for security reasons
> and technical perspective...
> regarding Access/ADO, you actually do not need this path as you could go
> with other model (c#/ADO.Net or whatever), but it's ok..
>
> it dependes on your code quality and logic... avoid SELECT * FROM
> myMillionTable and follow standard code quality and best practice for
> database applications
> you have to test your scenario...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Terry,
The answer is yes, giving that MSDE (SQL Server) is running on
workstation 1 (it is a program, not just a database "file") and that the
user on Workstation 2 has the necessary "rights" to access the database.
Lars Broberg
Elbe-Data AB
http://www.elbe-data.se
Remove "nothing." when replying to private e-mail!
Terry wrote:[vbcol=seagreen]
> Hello Andrea
> Thanks for the information.
> I think I worded the question badly in terms of sharing - I understand where
> you are coming from (I think). Can a user on, say Workstation 2 access the
> data in an MSDE database on Workstation 1?
> Terry
> =================================
> "Andrea Montanari" wrote:
>
sql
folder on a per-to-peer network.
1. Can we use MSDE to back-end the database and have up to five users access
it from each of their workstations if we change the front-end to an Access
project using ADO?
2. If this can be done how will the performance compare? There are up to 40
tables containing up to 150MB of data.
Thanks
Terry
hi Terry,
Terry wrote:
> We have a Front End/Back End database. The Back End is stored in a
> shared folder on a per-to-peer network.
> 1. Can we use MSDE to back-end the database and have up to five users
> access it from each of their workstations if we change the front-end
> to an Access project using ADO?
you should not store SQL Server/MSDE databases in a network share, nor
should they be on a remote one..
users only needs to access MSDE, and thus data throught it's service and do
not need physical access to the database os files, both for security reasons
and technical perspective...
regarding Access/ADO, you actually do not need this path as you could go
with other model (c#/ADO.Net or whatever), but it's ok..
> 2. If this can be done how will the performance compare? There are up
> to 40 tables containing up to 150MB of data.
it dependes on your code quality and logic... avoid SELECT * FROM
myMillionTable and follow standard code quality and best practice for
database applications
you have to test your scenario...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello Andrea
Thanks for the information.
I think I worded the question badly in terms of sharing - I understand where
you are coming from (I think). Can a user on, say Workstation 2 access the
data in an MSDE database on Workstation 1?
Terry
=================================
"Andrea Montanari" wrote:
> hi Terry,
> Terry wrote:
> you should not store SQL Server/MSDE databases in a network share, nor
> should they be on a remote one..
> users only needs to access MSDE, and thus data throught it's service and do
> not need physical access to the database os files, both for security reasons
> and technical perspective...
> regarding Access/ADO, you actually do not need this path as you could go
> with other model (c#/ADO.Net or whatever), but it's ok..
>
> it dependes on your code quality and logic... avoid SELECT * FROM
> myMillionTable and follow standard code quality and best practice for
> database applications
> you have to test your scenario...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Terry,
The answer is yes, giving that MSDE (SQL Server) is running on
workstation 1 (it is a program, not just a database "file") and that the
user on Workstation 2 has the necessary "rights" to access the database.
Lars Broberg
Elbe-Data AB
http://www.elbe-data.se
Remove "nothing." when replying to private e-mail!
Terry wrote:[vbcol=seagreen]
> Hello Andrea
> Thanks for the information.
> I think I worded the question badly in terms of sharing - I understand where
> you are coming from (I think). Can a user on, say Workstation 2 access the
> data in an MSDE database on Workstation 1?
> Terry
> =================================
> "Andrea Montanari" wrote:
>
sql
Monday, March 26, 2012
MSDE searching for servers on the network.
Hi,
I have a MSDE installation on the network. I have no need though to
talk to any other MSDE servers or visa versa.
Is it possible to stop MSDE looking for other servers on the network
and also stop other servers finding me?
Thanks
Lee
Hi Lee,
Run svrnetcn.exe and disable all network protocols. Access the MSDE using
shared memory instead (use server name (local) ), even choose the "Hide
Server" option in the properties of TCP in that screen.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Lee Farrant" <leefarrant@.hotmail.com> wrote in message
news:97ad5817.0409160016.4e99863a@.posting.google.c om...
> Hi,
> I have a MSDE installation on the network. I have no need though to
> talk to any other MSDE servers or visa versa.
> Is it possible to stop MSDE looking for other servers on the network
> and also stop other servers finding me?
> Thanks
> Lee
|||Hello Greg,
Thanks for your help I will have a look at these settings.
Lee
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message news:<eRyFDDInEHA.1672@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Hi Lee,
> Run svrnetcn.exe and disable all network protocols. Access the MSDE using
> shared memory instead (use server name (local) ), even choose the "Hide
> Server" option in the properties of TCP in that screen.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Lee Farrant" <leefarrant@.hotmail.com> wrote in message
> news:97ad5817.0409160016.4e99863a@.posting.google.c om...
I have a MSDE installation on the network. I have no need though to
talk to any other MSDE servers or visa versa.
Is it possible to stop MSDE looking for other servers on the network
and also stop other servers finding me?
Thanks
Lee
Hi Lee,
Run svrnetcn.exe and disable all network protocols. Access the MSDE using
shared memory instead (use server name (local) ), even choose the "Hide
Server" option in the properties of TCP in that screen.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Lee Farrant" <leefarrant@.hotmail.com> wrote in message
news:97ad5817.0409160016.4e99863a@.posting.google.c om...
> Hi,
> I have a MSDE installation on the network. I have no need though to
> talk to any other MSDE servers or visa versa.
> Is it possible to stop MSDE looking for other servers on the network
> and also stop other servers finding me?
> Thanks
> Lee
|||Hello Greg,
Thanks for your help I will have a look at these settings.
Lee
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message news:<eRyFDDInEHA.1672@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Hi Lee,
> Run svrnetcn.exe and disable all network protocols. Access the MSDE using
> shared memory instead (use server name (local) ), even choose the "Hide
> Server" option in the properties of TCP in that screen.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Lee Farrant" <leefarrant@.hotmail.com> wrote in message
> news:97ad5817.0409160016.4e99863a@.posting.google.c om...
Friday, March 23, 2012
MSDE over the network
Please help! I've had this problem for FOREVER. It's driving me batty.
I'm installing MSDE in a networked environment. I'm using SQL-DMO to find all
instances of MSDE on the network. *Usually*, this works great.
Unfortunately, sometimes MSDE instances refuse to advertise on the network.
I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
using setup.exe to install these instances, and I'm setting
DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
vanished instance is in fact listening via TCP/IP and Remote Procedure Calls.
I've added each instance as an exception in the Windows Firewall on XP SP2.
Each disappeared instance has in fact been started. Local applications can
see these vanished instances, but networked applications cannot. There are no
other firewalls or packet filtering on the network. I'm behind a Microsoft
Wireless Base Station Router. Am I missing something?
This problem is about to drive me insane. I'm using the exact same
installation program and parameters to setup.exe, but some instances just
don't want to play on the network. Any help would be greatly appreciated.
Thanks in advance.
Rob Reagan
rob at digitallabsinc.com
Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
not have SP3 installed then XP will block MSDE from broadcasting its status.
You can see warnings about this in the system event log. This is the same
with Windows Server 2003.
Jim
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> Please help! I've had this problem for FOREVER. It's driving me batty.
> I'm installing MSDE in a networked environment. I'm using SQL-DMO to find
all
> instances of MSDE on the network. *Usually*, this works great.
> Unfortunately, sometimes MSDE instances refuse to advertise on the
network.
> I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
> using setup.exe to install these instances, and I'm setting
> DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
> vanished instance is in fact listening via TCP/IP and Remote Procedure
Calls.
> I've added each instance as an exception in the Windows Firewall on XP
SP2.
> Each disappeared instance has in fact been started. Local applications can
> see these vanished instances, but networked applications cannot. There are
no
> other firewalls or packet filtering on the network. I'm behind a Microsoft
> Wireless Base Station Router. Am I missing something?
> This problem is about to drive me insane. I'm using the exact same
> installation program and parameters to setup.exe, but some instances just
> don't want to play on the network. Any help would be greatly appreciated.
> Thanks in advance.
> Rob Reagan
> rob at digitallabsinc.com
>
|||YOU ARE THE MAN! Thanks so much for that response.
"Jim Young" wrote:
> Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
> not have SP3 installed then XP will block MSDE from broadcasting its status.
> You can see warnings about this in the system event log. This is the same
> with Windows Server 2003.
> Jim
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
> news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> all
> network.
> Calls.
> SP2.
> no
>
>
I'm installing MSDE in a networked environment. I'm using SQL-DMO to find all
instances of MSDE on the network. *Usually*, this works great.
Unfortunately, sometimes MSDE instances refuse to advertise on the network.
I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
using setup.exe to install these instances, and I'm setting
DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
vanished instance is in fact listening via TCP/IP and Remote Procedure Calls.
I've added each instance as an exception in the Windows Firewall on XP SP2.
Each disappeared instance has in fact been started. Local applications can
see these vanished instances, but networked applications cannot. There are no
other firewalls or packet filtering on the network. I'm behind a Microsoft
Wireless Base Station Router. Am I missing something?
This problem is about to drive me insane. I'm using the exact same
installation program and parameters to setup.exe, but some instances just
don't want to play on the network. Any help would be greatly appreciated.
Thanks in advance.
Rob Reagan
rob at digitallabsinc.com
Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
not have SP3 installed then XP will block MSDE from broadcasting its status.
You can see warnings about this in the system event log. This is the same
with Windows Server 2003.
Jim
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> Please help! I've had this problem for FOREVER. It's driving me batty.
> I'm installing MSDE in a networked environment. I'm using SQL-DMO to find
all
> instances of MSDE on the network. *Usually*, this works great.
> Unfortunately, sometimes MSDE instances refuse to advertise on the
network.
> I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
> using setup.exe to install these instances, and I'm setting
> DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
> vanished instance is in fact listening via TCP/IP and Remote Procedure
Calls.
> I've added each instance as an exception in the Windows Firewall on XP
SP2.
> Each disappeared instance has in fact been started. Local applications can
> see these vanished instances, but networked applications cannot. There are
no
> other firewalls or packet filtering on the network. I'm behind a Microsoft
> Wireless Base Station Router. Am I missing something?
> This problem is about to drive me insane. I'm using the exact same
> installation program and parameters to setup.exe, but some instances just
> don't want to play on the network. Any help would be greatly appreciated.
> Thanks in advance.
> Rob Reagan
> rob at digitallabsinc.com
>
|||YOU ARE THE MAN! Thanks so much for that response.
"Jim Young" wrote:
> Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
> not have SP3 installed then XP will block MSDE from broadcasting its status.
> You can see warnings about this in the system event log. This is the same
> with Windows Server 2003.
> Jim
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
> news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> all
> network.
> Calls.
> SP2.
> no
>
>
MSDE over Novell network
I have an application that works fine on windows XP / windows network but I cannot get clients to find the database over a novell network one of the error messages is
Error -2147467259:[DBNMPNTW][Connectionopen (createfile())
Any help appreciated
David
PS all computers in the Novell network Win 2000
"DJS" wrote:
> I have an application that works fine on windows XP / windows network but I cannot get clients to find the database over a novell network one of the error messages is
> Error -2147467259:[DBNMPNTW][Connectionopen (createfile())
> Any help appreciated
> David
>
Error -2147467259:[DBNMPNTW][Connectionopen (createfile())
Any help appreciated
David
PS all computers in the Novell network Win 2000
"DJS" wrote:
> I have an application that works fine on windows XP / windows network but I cannot get clients to find the database over a novell network one of the error messages is
> Error -2147467259:[DBNMPNTW][Connectionopen (createfile())
> Any help appreciated
> David
>
Wednesday, March 21, 2012
MSDE or SQL-SERVER ?? help
Hello can someone help me out, i need to know if i buy the 5 User Cal license of MS-SQL server, does that mean that only 5 people on the network or through the web can access the database? Is that true?
How can i use the SQL Server in the following way:
2-4 users running on a local area network
10-15 concurrent users online
Database size will grow each year by 800-1000mb, i know the MSDE limit is 2Gig,
How can i get a solution to the above problem? what is my best bet to utilize SQL-Server? MSDE Or some other type of sql product?
MSDE has been shown to support far more than 10-15 users. It all depends on
how well the application is written and how your code manages the connection
and the server resource. SQL Express which is due out in 2005 ups the limit
to 4GB. However, with appropriate archiving, you can keep within the limits.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Artmic" <Artmic@.discussions.microsoft.com> wrote in message
news:703D7809-DB32-4557-825D-0C7F1F689BEC@.microsoft.com...
> Hello can someone help me out, i need to know if i buy the 5 User Cal
license of MS-SQL server, does that mean that only 5 people on the network
or through the web can access the database? Is that true?
> How can i use the SQL Server in the following way:
> 2-4 users running on a local area network
> 10-15 concurrent users online
> Database size will grow each year by 800-1000mb, i know the MSDE limit is
2Gig,
> How can i get a solution to the above problem? what is my best bet to
utilize SQL-Server? MSDE Or some other type of sql product?
>
|||Ok thanks, i guess i will go ahead with the MSDE and switch to SQL Express when it is available... it is just not economic for a small site to buy a multi-thousand dollar processor license for Online volume that is laughable IMO.
"William (Bill) Vaughn" wrote:
> MSDE has been shown to support far more than 10-15 users. It all depends on
> how well the application is written and how your code manages the connection
> and the server resource. SQL Express which is due out in 2005 ups the limit
> to 4GB. However, with appropriate archiving, you can keep within the limits.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> "Artmic" <Artmic@.discussions.microsoft.com> wrote in message
> news:703D7809-DB32-4557-825D-0C7F1F689BEC@.microsoft.com...
> license of MS-SQL server, does that mean that only 5 people on the network
> or through the web can access the database? Is that true?
> 2Gig,
> utilize SQL-Server? MSDE Or some other type of sql product?
>
>
How can i use the SQL Server in the following way:
2-4 users running on a local area network
10-15 concurrent users online
Database size will grow each year by 800-1000mb, i know the MSDE limit is 2Gig,
How can i get a solution to the above problem? what is my best bet to utilize SQL-Server? MSDE Or some other type of sql product?
MSDE has been shown to support far more than 10-15 users. It all depends on
how well the application is written and how your code manages the connection
and the server resource. SQL Express which is due out in 2005 ups the limit
to 4GB. However, with appropriate archiving, you can keep within the limits.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Artmic" <Artmic@.discussions.microsoft.com> wrote in message
news:703D7809-DB32-4557-825D-0C7F1F689BEC@.microsoft.com...
> Hello can someone help me out, i need to know if i buy the 5 User Cal
license of MS-SQL server, does that mean that only 5 people on the network
or through the web can access the database? Is that true?
> How can i use the SQL Server in the following way:
> 2-4 users running on a local area network
> 10-15 concurrent users online
> Database size will grow each year by 800-1000mb, i know the MSDE limit is
2Gig,
> How can i get a solution to the above problem? what is my best bet to
utilize SQL-Server? MSDE Or some other type of sql product?
>
|||Ok thanks, i guess i will go ahead with the MSDE and switch to SQL Express when it is available... it is just not economic for a small site to buy a multi-thousand dollar processor license for Online volume that is laughable IMO.
"William (Bill) Vaughn" wrote:
> MSDE has been shown to support far more than 10-15 users. It all depends on
> how well the application is written and how your code manages the connection
> and the server resource. SQL Express which is due out in 2005 ups the limit
> to 4GB. However, with appropriate archiving, you can keep within the limits.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> "Artmic" <Artmic@.discussions.microsoft.com> wrote in message
> news:703D7809-DB32-4557-825D-0C7F1F689BEC@.microsoft.com...
> license of MS-SQL server, does that mean that only 5 people on the network
> or through the web can access the database? Is that true?
> 2Gig,
> utilize SQL-Server? MSDE Or some other type of sql product?
>
>
MSDE on SBS2003 from Network
I have created a new MSDE instance on my SBS 2003 Standard server, using
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:
>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.
>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?
>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:
>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?
>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:
>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:
>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.
>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?
>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:
>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?
>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:
>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)
Monday, March 19, 2012
MSDE not accepting connection
I recently installed MSDE SP3 on a laptop. Everything works fine,
except when I unplug the laptop from my network.
If I boot up my laptop when I am not connected to a network, I can't
connect to MSDE. I've tried TCP/IP and Named Pipes. When I plug in my
network cable, MSDE starts accepting connections.
The error is: SQL Server does not exist or access denied
I'm using Query Analyzer for testing the connection.
I can ping 127.0.0.1, so the loopback adapter is running OK.
I have no firewall software running on the computer.
I have installed MSDE with DISABLENETWORKPROTOCOLS=0 and
SECURITYMODE=SQL.
I'm running XP sp1 with all critical updates from windowsupdate.
Any help appreciated.
Finn Bjornsen
Enable the Shared Memory protocol for MSDE.
Jim
"Finn Bjornsen" <finnbi@.talent.dk> wrote in message
news:e9f3a153.0404220036.39d45ae3@.posting.google.c om...
> I recently installed MSDE SP3 on a laptop. Everything works fine,
> except when I unplug the laptop from my network.
> If I boot up my laptop when I am not connected to a network, I can't
> connect to MSDE. I've tried TCP/IP and Named Pipes. When I plug in my
> network cable, MSDE starts accepting connections.
> The error is: SQL Server does not exist or access denied
> I'm using Query Analyzer for testing the connection.
> I can ping 127.0.0.1, so the loopback adapter is running OK.
> I have no firewall software running on the computer.
> I have installed MSDE with DISABLENETWORKPROTOCOLS=0 and
> SECURITYMODE=SQL.
> I'm running XP sp1 with all critical updates from windowsupdate.
> Any help appreciated.
> Finn Bjornsen
|||Thanks for your advice.
Shared Memory Protocol is enabled on the client (Query Analyzer).
I don't think there is a problem with the client. It's most like a
problem with the server (MSDE) or the operating system (Windows XP)
Regards
Finn Bjornsen
|||Hi Finn,
I also had similar problem and posted the question ('Problem installing pubs
db in MSDE') before seeing your posting. So I was just watching your post
and replies.
My problem was solved by using both computer name and instance name
separated by a back-slash as:
<ComputerName>\<InstanceName>
Try it and see.
ThanQ...
"Finn Bjornsen" <finnbi@.talent.dk> wrote in message
news:e9f3a153.0404222212.55fd1301@.posting.google.c om...
> Thanks for your advice.
> Shared Memory Protocol is enabled on the client (Query Analyzer).
> I don't think there is a problem with the client. It's most like a
> problem with the server (MSDE) or the operating system (Windows XP)
> Regards
> Finn Bjornsen
|||I use a default instance.
Tried using 127.0.0.1\
Didn't work. Still not able to connect.
It can't be true. MSDE has be able to function on a laptop even though
the network cable has been unplugged.
except when I unplug the laptop from my network.
If I boot up my laptop when I am not connected to a network, I can't
connect to MSDE. I've tried TCP/IP and Named Pipes. When I plug in my
network cable, MSDE starts accepting connections.
The error is: SQL Server does not exist or access denied
I'm using Query Analyzer for testing the connection.
I can ping 127.0.0.1, so the loopback adapter is running OK.
I have no firewall software running on the computer.
I have installed MSDE with DISABLENETWORKPROTOCOLS=0 and
SECURITYMODE=SQL.
I'm running XP sp1 with all critical updates from windowsupdate.
Any help appreciated.
Finn Bjornsen
Enable the Shared Memory protocol for MSDE.
Jim
"Finn Bjornsen" <finnbi@.talent.dk> wrote in message
news:e9f3a153.0404220036.39d45ae3@.posting.google.c om...
> I recently installed MSDE SP3 on a laptop. Everything works fine,
> except when I unplug the laptop from my network.
> If I boot up my laptop when I am not connected to a network, I can't
> connect to MSDE. I've tried TCP/IP and Named Pipes. When I plug in my
> network cable, MSDE starts accepting connections.
> The error is: SQL Server does not exist or access denied
> I'm using Query Analyzer for testing the connection.
> I can ping 127.0.0.1, so the loopback adapter is running OK.
> I have no firewall software running on the computer.
> I have installed MSDE with DISABLENETWORKPROTOCOLS=0 and
> SECURITYMODE=SQL.
> I'm running XP sp1 with all critical updates from windowsupdate.
> Any help appreciated.
> Finn Bjornsen
|||Thanks for your advice.
Shared Memory Protocol is enabled on the client (Query Analyzer).
I don't think there is a problem with the client. It's most like a
problem with the server (MSDE) or the operating system (Windows XP)
Regards
Finn Bjornsen
|||Hi Finn,
I also had similar problem and posted the question ('Problem installing pubs
db in MSDE') before seeing your posting. So I was just watching your post
and replies.
My problem was solved by using both computer name and instance name
separated by a back-slash as:
<ComputerName>\<InstanceName>
Try it and see.
ThanQ...
"Finn Bjornsen" <finnbi@.talent.dk> wrote in message
news:e9f3a153.0404222212.55fd1301@.posting.google.c om...
> Thanks for your advice.
> Shared Memory Protocol is enabled on the client (Query Analyzer).
> I don't think there is a problem with the client. It's most like a
> problem with the server (MSDE) or the operating system (Windows XP)
> Regards
> Finn Bjornsen
|||I use a default instance.
Tried using 127.0.0.1\
Didn't work. Still not able to connect.
It can't be true. MSDE has be able to function on a laptop even though
the network cable has been unplugged.
MSDE newbie question: connection strings
I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
domain controller.
If I access this database via ADO, how do I construct the connection
string? As I understand it, this is of the form:
Provider=SQLOLEDB; Data Source=server_name; Initial
Catalog=database_name; User ID=username; Password=password;
Is the server name just the name or IP address of the PC running MSDE?
Are there any other subtleties I should be aware of?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:OuUGwZwQEHA.3580@.TK2MSFTNGP11.phx.gbl...
> I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
> domain controller.
> If I access this database via ADO, how do I construct the connection
> string? As I understand it, this is of the form:
> Provider=SQLOLEDB; Data Source=server_name; Initial
> Catalog=database_name; User ID=username; Password=password;
> Is the server name just the name or IP address of the PC running MSDE?
> Are there any other subtleties I should be aware of?
if the MSDE instance has been installed as the default intance, it's name
will just be the ComputerName and/or it's IP address... if it has been
installed as a named instance, it's name will be
ComputerName\InstanceName...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
domain controller.
If I access this database via ADO, how do I construct the connection
string? As I understand it, this is of the form:
Provider=SQLOLEDB; Data Source=server_name; Initial
Catalog=database_name; User ID=username; Password=password;
Is the server name just the name or IP address of the PC running MSDE?
Are there any other subtleties I should be aware of?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:OuUGwZwQEHA.3580@.TK2MSFTNGP11.phx.gbl...
> I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
> domain controller.
> If I access this database via ADO, how do I construct the connection
> string? As I understand it, this is of the form:
> Provider=SQLOLEDB; Data Source=server_name; Initial
> Catalog=database_name; User ID=username; Password=password;
> Is the server name just the name or IP address of the PC running MSDE?
> Are there any other subtleties I should be aware of?
if the MSDE instance has been installed as the default intance, it's name
will just be the ComputerName and/or it's IP address... if it has been
installed as a named instance, it's name will be
ComputerName\InstanceName...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE login problem
After installing MSDE 2000 in mixed mode local access worked fine.
Accessing through network with enterprice manager at first didn't work.
Fixed by activating network protocols "TCP/IP" and "Named pipes" in database properties.
But only the first time. After that login by SQL user and password is denied after restart local MSDE machine.
Accessing through network with enterprice manager at first didn't work.
Fixed by activating network protocols "TCP/IP" and "Named pipes" in database properties.
But only the first time. After that login by SQL user and password is denied after restart local MSDE machine.
Anyone know why?
thanks in advanceAfter that login by SQL user and password is denied after restart local MSDE machine
With this I mean access from other machines on the network. Local login is working ok.|||Solution found!
Install MSDE again with DISABLENETWORKPROTOCOLS=0.
Changing it afterwards with SQL Server enterprice manager doesn't work.
just for those who are having the same problem
Monday, March 12, 2012
msde licence
we get from a company installed at our customer sides an application using
msde in a win 2000 server (terminal) or higher network enwironment. We have a
lot of troubles because this application is going to let our application fail
often , and we get a lot of instability.
Hi rudolph,
Sorry, but dont' see a question here. Why do you think that the MSDE is
causing instability for your app?
Regards,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"rudolph" <rudolph@.discussions.microsoft.com> wrote in message
news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
> we get from a company installed at our customer sides an application using
> msde in a win 2000 server (terminal) or higher network enwironment. We
> have a
> lot of troubles because this application is going to let our application
> fail
> often , and we get a lot of instability.
|||Hi Greg!
My question is, that we have done out of a pervasive sql based application
an Interface to a small application. This small application is using msde in
a enviroment, we are using, win 2003 or winn200 Server with terminal clients.
The company, who has done the small aplication we are interfacing has
installed at our clients side either msde or MSSQL Server products, depending
on their stability.We have not been asked by them what they are going to
install I thought, that msde is a client product and not a server product. IS
msde a product which can run simitaniosly in our environment?
"Greg Low [MVP]" wrote:
> Hi rudolph,
> Sorry, but dont' see a question here. Why do you think that the MSDE is
> causing instability for your app?
> Regards,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "rudolph" <rudolph@.discussions.microsoft.com> wrote in message
> news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
>
>
|||hi Rudolph,
rudolph wrote:
> Hi Greg!
> My question is, that we have done out of a pervasive sql based
> application an Interface to a small application. This small
> application is using msde in a enviroment, we are using, win 2003 or
> winn200 Server with terminal clients. The company, who has done the
> small aplication we are interfacing has installed at our clients side
> either msde or MSSQL Server products, depending on their stability. We
> have not been asked by them what they are going to install I thought,
> that msde is a client product and not a server product. IS msde a
> product which can run simitaniosly in our environment?
I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
problems...
MSDE is one of the editions of SQL Server, limited some way, but shares the
same core functionnalities and features...
MSDE is not a client product as Access, it's a "scaled down" version of a
full blown "enterprise" DBMS, with built-in limitation for database size,
concurrent workloads, and so on...
as regard as your last question,
>IS msde a
> product which can run simitaniosly in our environment?
I should say yes, but your environment is not public , and of course it
all depends on your requirements..
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Rudolph,
And to add to what Andrea said, we've used it in that sort of environment
many, many times without issue.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:35pbuqF4pmdlaU1@.individual.net...
> hi Rudolph,
> rudolph wrote:
> I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
> problems...
> MSDE is one of the editions of SQL Server, limited some way, but shares
> the
> same core functionnalities and features...
> MSDE is not a client product as Access, it's a "scaled down" version of a
> full blown "enterprise" DBMS, with built-in limitation for database size,
> concurrent workloads, and so on...
> as regard as your last question,
> I should say yes, but your environment is not public , and of course it
> all depends on your requirements..
> regards
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
msde in a win 2000 server (terminal) or higher network enwironment. We have a
lot of troubles because this application is going to let our application fail
often , and we get a lot of instability.
Hi rudolph,
Sorry, but dont' see a question here. Why do you think that the MSDE is
causing instability for your app?
Regards,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"rudolph" <rudolph@.discussions.microsoft.com> wrote in message
news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
> we get from a company installed at our customer sides an application using
> msde in a win 2000 server (terminal) or higher network enwironment. We
> have a
> lot of troubles because this application is going to let our application
> fail
> often , and we get a lot of instability.
|||Hi Greg!
My question is, that we have done out of a pervasive sql based application
an Interface to a small application. This small application is using msde in
a enviroment, we are using, win 2003 or winn200 Server with terminal clients.
The company, who has done the small aplication we are interfacing has
installed at our clients side either msde or MSSQL Server products, depending
on their stability.We have not been asked by them what they are going to
install I thought, that msde is a client product and not a server product. IS
msde a product which can run simitaniosly in our environment?
"Greg Low [MVP]" wrote:
> Hi rudolph,
> Sorry, but dont' see a question here. Why do you think that the MSDE is
> causing instability for your app?
> Regards,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "rudolph" <rudolph@.discussions.microsoft.com> wrote in message
> news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
>
>
|||hi Rudolph,
rudolph wrote:
> Hi Greg!
> My question is, that we have done out of a pervasive sql based
> application an Interface to a small application. This small
> application is using msde in a enviroment, we are using, win 2003 or
> winn200 Server with terminal clients. The company, who has done the
> small aplication we are interfacing has installed at our clients side
> either msde or MSSQL Server products, depending on their stability. We
> have not been asked by them what they are going to install I thought,
> that msde is a client product and not a server product. IS msde a
> product which can run simitaniosly in our environment?
I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
problems...
MSDE is one of the editions of SQL Server, limited some way, but shares the
same core functionnalities and features...
MSDE is not a client product as Access, it's a "scaled down" version of a
full blown "enterprise" DBMS, with built-in limitation for database size,
concurrent workloads, and so on...
as regard as your last question,
>IS msde a
> product which can run simitaniosly in our environment?
I should say yes, but your environment is not public
, and of course itall depends on your requirements..
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Rudolph,
And to add to what Andrea said, we've used it in that sort of environment
many, many times without issue.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:35pbuqF4pmdlaU1@.individual.net...
> hi Rudolph,
> rudolph wrote:
> I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
> problems...
> MSDE is one of the editions of SQL Server, limited some way, but shares
> the
> same core functionnalities and features...
> MSDE is not a client product as Access, it's a "scaled down" version of a
> full blown "enterprise" DBMS, with built-in limitation for database size,
> concurrent workloads, and so on...
> as regard as your last question,
> I should say yes, but your environment is not public
, and of course it> all depends on your requirements..
> regards
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Friday, March 9, 2012
MSDE Installation on a XP Professional WS.
Hello,
I'm experiencing 2 problems after MSDE installation on a XP Pro workstation
on a network.
1. The SQL Service Manager don't show the default instance. If I put
manually is OK, but on every reboot it lose the instance name and show me
nothing.
2. it's impossible to login from an external computer or create any kind of
connection (ODBC or .udl file).
For information the setup was make:
with an .ini file containing
[Options]
INSTANCENAME=fgsoftware
SAPWD=xyzxyz
SECURITYMODE=SQL
The computer is SP2 full patched.
After the first problems I deactivated the windows firewall.
Help me!!!
TIA
Francesco Garganese
FG software
Can't help you with 1 unfortunately - it has happened to me but I've never
quite worked out why...
To log in from an external computer you need to have set the
DISABLENETWORKPROTOLS flag to false when installing. See the readme that
comes with the installer for more details on command line switches.
Also, MSDE from Service Pack 3a onwards, installs in Windows Authentication
mode only by default. see the following kb article for more info:
http://support.microsoft.com/default...;EN-US;Q325022
If you're trying to access it from another machine that is not logged in as
a *domain* user on the same domain (i.e. you must be running a Windows 2003
Server Domain Controller somewhere) then you can only connect using Mixed
Mode Authentication, which as the above article will tell you is disabled by
default.
"Francesco Garganese" <FrancescoGarganese@.discussions.microsoft.com> wrote
in message news:CD18E7C6-6E32-4D27-974D-C744C580C820@.microsoft.com...
> Hello,
> I'm experiencing 2 problems after MSDE installation on a XP Pro
> workstation
> on a network.
> 1. The SQL Service Manager don't show the default instance. If I put
> manually is OK, but on every reboot it lose the instance name and show me
> nothing.
> 2. it's impossible to login from an external computer or create any kind
> of
> connection (ODBC or .udl file).
> For information the setup was make:
> with an .ini file containing
> [Options]
> INSTANCENAME=fgsoftware
> SAPWD=xyzxyz
> SECURITYMODE=SQL
> The computer is SP2 full patched.
> After the first problems I deactivated the windows firewall.
> Help me!!!
> TIA
> --
> Francesco Garganese
> FG software
|||Thank you very much Ben, adding DISABLENETWORKPROTOLS=0 in the paramenters
and reinstalling both problems are resolved!
Sincerely
Francesco Garganese
FG software
I'm experiencing 2 problems after MSDE installation on a XP Pro workstation
on a network.
1. The SQL Service Manager don't show the default instance. If I put
manually is OK, but on every reboot it lose the instance name and show me
nothing.
2. it's impossible to login from an external computer or create any kind of
connection (ODBC or .udl file).
For information the setup was make:
with an .ini file containing
[Options]
INSTANCENAME=fgsoftware
SAPWD=xyzxyz
SECURITYMODE=SQL
The computer is SP2 full patched.
After the first problems I deactivated the windows firewall.
Help me!!!
TIA
Francesco Garganese
FG software
Can't help you with 1 unfortunately - it has happened to me but I've never
quite worked out why...
To log in from an external computer you need to have set the
DISABLENETWORKPROTOLS flag to false when installing. See the readme that
comes with the installer for more details on command line switches.
Also, MSDE from Service Pack 3a onwards, installs in Windows Authentication
mode only by default. see the following kb article for more info:
http://support.microsoft.com/default...;EN-US;Q325022
If you're trying to access it from another machine that is not logged in as
a *domain* user on the same domain (i.e. you must be running a Windows 2003
Server Domain Controller somewhere) then you can only connect using Mixed
Mode Authentication, which as the above article will tell you is disabled by
default.
"Francesco Garganese" <FrancescoGarganese@.discussions.microsoft.com> wrote
in message news:CD18E7C6-6E32-4D27-974D-C744C580C820@.microsoft.com...
> Hello,
> I'm experiencing 2 problems after MSDE installation on a XP Pro
> workstation
> on a network.
> 1. The SQL Service Manager don't show the default instance. If I put
> manually is OK, but on every reboot it lose the instance name and show me
> nothing.
> 2. it's impossible to login from an external computer or create any kind
> of
> connection (ODBC or .udl file).
> For information the setup was make:
> with an .ini file containing
> [Options]
> INSTANCENAME=fgsoftware
> SAPWD=xyzxyz
> SECURITYMODE=SQL
> The computer is SP2 full patched.
> After the first problems I deactivated the windows firewall.
> Help me!!!
> TIA
> --
> Francesco Garganese
> FG software
|||Thank you very much Ben, adding DISABLENETWORKPROTOLS=0 in the paramenters
and reinstalling both problems are resolved!
Sincerely
Francesco Garganese
FG software
Wednesday, March 7, 2012
MSDE Installation
Hello,
How can I install msde without the office disk. Access was installed through
the network so i do not have a copy of the disk. Is it available anwhere else?
Thanks
Yes you can download from MS, try this link...
http://www.microsoft.com/downloads/d...DisplayLang=en
Hope this helps...
wardeaux
"burg" <burg@.discussions.microsoft.com> wrote in message
news:8B25659F-4967-4BF6-831B-8D33062AB135@.microsoft.com...
> Hello,
> How can I install msde without the office disk. Access was installed
through
> the network so i do not have a copy of the disk. Is it available anwhere
else?
> Thanks
|||Thank you. That was exactly what i needed.
"Wardeaux" wrote:
> Yes you can download from MS, try this link...
> http://www.microsoft.com/downloads/d...DisplayLang=en
> Hope this helps...
> wardeaux
> "burg" <burg@.discussions.microsoft.com> wrote in message
> news:8B25659F-4967-4BF6-831B-8D33062AB135@.microsoft.com...
> through
> else?
>
>
How can I install msde without the office disk. Access was installed through
the network so i do not have a copy of the disk. Is it available anwhere else?
Thanks
Yes you can download from MS, try this link...
http://www.microsoft.com/downloads/d...DisplayLang=en
Hope this helps...
wardeaux
"burg" <burg@.discussions.microsoft.com> wrote in message
news:8B25659F-4967-4BF6-831B-8D33062AB135@.microsoft.com...
> Hello,
> How can I install msde without the office disk. Access was installed
through
> the network so i do not have a copy of the disk. Is it available anwhere
else?
> Thanks
|||Thank you. That was exactly what i needed.
"Wardeaux" wrote:
> Yes you can download from MS, try this link...
> http://www.microsoft.com/downloads/d...DisplayLang=en
> Hope this helps...
> wardeaux
> "burg" <burg@.discussions.microsoft.com> wrote in message
> news:8B25659F-4967-4BF6-831B-8D33062AB135@.microsoft.com...
> through
> else?
>
>
Saturday, February 25, 2012
MSDE in WinXP Pro SP2
I have installed MSDE in WinXP Professional SP2, and already enabled the
TCP/IP protocol in SQL Server Network Utility. However, I find that it is
failure to connect the database by calling the IP Address even I test it
locally (use sa/window authorization) , but it is ok by calling the computer
name or (local) (also use sa/window authorization) . I have disabled the
firewall and the situation is no change.
Anyone have same experience on this case?
> Anyone have same experience on this case?
Yes, I have. But I have no answer how to fix it. There must be a bug
somwhere.
Regards,
Lars-Inge Tonnessen
TCP/IP protocol in SQL Server Network Utility. However, I find that it is
failure to connect the database by calling the IP Address even I test it
locally (use sa/window authorization) , but it is ok by calling the computer
name or (local) (also use sa/window authorization) . I have disabled the
firewall and the situation is no change.
Anyone have same experience on this case?
> Anyone have same experience on this case?
Yes, I have. But I have no answer how to fix it. There must be a bug
somwhere.
Regards,
Lars-Inge Tonnessen
Monday, February 20, 2012
MSDE for Small Network System
Is it appropriate of using MSDE for peer to peer network system of a few computers, commercially?
All computers are working on Windows XP Pro, sharing DB each other via MSDE.
Are there anyone to advice us regarding the technical problems or licence problems?
Hi,
You can use MSDE on the peer to peer network. There are no licensing
issues, as MSDE is available free of cost and can be freely downloaded from
http://www.microsoft.com/sql/msde/do...s/download.asp
The technical issues that you may face are
1. There is not frontend for MSDE. you can use Web Data Administrator tool.
It can be downloaded from
http://www.microsoft.com/downloads/d...798-C57A-419E-
ACBC-2A332CB7F959&displaylang=en
2. The data size in MSDE is limited to 2GB. The data cannot grow beyond 2
GB in an MSDE database.
3. MSDE has a workload governor that gets activated when there are more
than 8 process running simultaneously on an instance of MSDE. The workload
governor slows down the response of the MSDE instance. However, it does not
stop from multiple users using it. for more information on Workload
governor please visit
http://msdn.microsoft.com/library/?u.../8_ar_sa2_0ciq
.asp?frame=true
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
All computers are working on Windows XP Pro, sharing DB each other via MSDE.
Are there anyone to advice us regarding the technical problems or licence problems?
Hi,
You can use MSDE on the peer to peer network. There are no licensing
issues, as MSDE is available free of cost and can be freely downloaded from
http://www.microsoft.com/sql/msde/do...s/download.asp
The technical issues that you may face are
1. There is not frontend for MSDE. you can use Web Data Administrator tool.
It can be downloaded from
http://www.microsoft.com/downloads/d...798-C57A-419E-
ACBC-2A332CB7F959&displaylang=en
2. The data size in MSDE is limited to 2GB. The data cannot grow beyond 2
GB in an MSDE database.
3. MSDE has a workload governor that gets activated when there are more
than 8 process running simultaneously on an instance of MSDE. The workload
governor slows down the response of the MSDE instance. However, it does not
stop from multiple users using it. for more information on Workload
governor please visit
http://msdn.microsoft.com/library/?u.../8_ar_sa2_0ciq
.asp?frame=true
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)