Simple(?) Question...

  • Thread starter Thread starter Wardeaux
  • Start date Start date
W

Wardeaux

Hey all,
Somewhat new to ADO.NET... I've developed an enterprise ASP.NET app that
uses SQL Server 2000. I now want to retail the app to smaller customers but
don't want to require all customers to license their own SQL Server ($$$$).
I would like to have one set of code that will run with either SQL Server
2000 or MSDE 2000.
1) Is this an easy task or is there a lot of coding involved?
2) Are there any articles that outline coding differences or is it simply an
"install and config" issue on the server?
3) Can I load my SQL Server 2000 DB into MSDE or are there difficulties
going backwards?

Many thanks in advance!
wardeaux
 
Comments below:
Wardeaux said:
Hey all,
Somewhat new to ADO.NET... I've developed an enterprise ASP.NET app that
uses SQL Server 2000. I now want to retail the app to smaller customers but
don't want to require all customers to license their own SQL Server ($$$$).
I would like to have one set of code that will run with either SQL Server
2000 or MSDE 2000.
1) Is this an easy task or is there a lot of coding involved?
Click to expand...

There's no difference at all code wise, the only difference will be on the
install. One you install the full SQL Server, the other you install MSDEE
2) Are there any articles that outline coding differences or is it simply an
"install and config" issue on the server? There aren't any
3) Can I load my SQL Server 2000 DB into MSDE or are there difficulties
going backwards?
Click to expand...
Yes, no problems at all. The 'real' differences are MSDE's limit of a 2gb
size for instance. For the most part, the differences are transparent..
both use SQL Client, both use T-SQL etc etc
 
William,
thanks for the reply! Does the MSDE have to be installed on the
Webserver? I've installed it on my workstation, and I can't connect to it
from anywhere except from my workstation? Or is this likely just a
permissions thing? The error says "can't find server or access denied."...
ANy clues?
thanks!
wardeaux
 
I doesn't have ot be on the web server, it's a real client/server db. It's
a permissions thing almost for sure. Are you using trusted connection or
mixed mode authentication?
 
Mixed-mode...
Hmmm.... I can connect fine from the webserver when MSDE is loaded on the
webserver, and I can connect from my workstation to my MSDE on my
workstation, but can't connect server to workstation or workstation to
server... (server is Win2K3 and workstation is WinXPPro) any clue which
permission is not set correctly? ;)
M,MTIA
wardeaux
 
And you've verified that the account you are trying to connect with in your
connectionstring has all the permissions right? Often, it will work b/c you
as a user are authenticated, but your connectionstring will specify Trusted
Connection = true or SSPI and that will account for the difference when you
try to run on a web server.
 
william,
thanks for working this with me!
I'm afraid i haven't even gotten to the "connectionString" part... I'm just
trying to connect to my workstation MSDE with the EnterpriseManager on my
server... I try to register a new server, give it the name of the MSDE on my
workstation, and I get the error: "<Servername> - SQL Server does not exist
or access denied. ConnectionOpen(Connect()" and yet I can register the
local MSDE instance (on the same server) just fine... I also cannot use
EnterpriseManager from my workstation and connect to the MSDE instance on my
server... I'm confident I'm not misspelling the server name, uid or
password,... any other possible suggestions?
wardeaux
 
By default MSDE 2000 sp3 installs with network connectivity disabled (due to
virus concerns).

Check the MSDE readme for info on how to install with network connectivity
enabled.
 
Jim nailed it. That totally slipped my mind but he's right, it's almost
certianly the problem.
 
Jim,
many MANY "thank you"s. That was it...

William,
Thanks so much for working that issue with me and hanging in there...
wardeaux
 
Back
Top