Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
stephenbaer
Yak Posting Veteran
71 Posts |
 Posted - 2006-08-02 : 14:48:40
|
| I'm fairly new to this SQL thing, and developing a database for a local nonprofit. I'm worried about killing a mision-critical HR application. It's a piece of commercial timeclock software that has an ASP (I think) front end and an MSDE backend. Since the budget is nonexistent, I'd like to piggyback my database on the existing MSDE engine. I'm not quite sure what 'instances' are, but I do know that MSDE can support multiple databases. I'm fairly certain that the commercial software uses SQL authentication, and mine will be using NT. I do know that the existing app is running in mixed mode, so the trusted connections will work, and should be secure as long as I don't grant any access to the other database, or mess with its security at all. My question then, is should I create a new instance, in order to separate the two, or just attach my mdf to whats already there? I hope I'm using these terms correctly. Please help.Gary Getsum: What happened to my mule?DM: It's dead; It got stung by a giant wasp. Gary: Can't I heal it?DM: I'm sorry, I know you were fond of the mule, but it just got attacked by a wasp the size of a Volkswagen!Gary: So?DM: Dude, look- you're going to have to carry all your own treasure now... Your mule gives new meaning to the term "Puff Daddy". |
|
|
peter_mauger
Starting Member
2 Posts |
Posted - 2006-08-07 : 23:22:35
|
| Ok, if you are worried about effecting the existing MSDE engine then you should absolutely go for a new instance. MSDE can be installed free of charge so there is no worries about cost (there is a limit to the number of instances that you can install... I think 8 is the max). To install a new instance open up the setup.ini file in the folder that your MSDE setup.exe is located.Change the contents to look something like:[Options]INSTANCENAME="<the name that you want to give your instance>"SAPWD="<your sa password for this instance... ideally the same as the other instance>"DISABLENETWORKPROTOCOLS=0 <this allows access from other computers on the network. If the application is only going to be run from the local computer then leave this line out>SECURITYMODE=SQL <this will give you mixed mode access. Leave this line out if you only want to use NT logins. Note that your sa password won't work if you use NT logins only (because it's an SQL login)>If that's a little confusing then go to http://www.codeproject.com/database/ConfigureMSDE.asp and everything will be explained.In your code you'll need to use a connection string along the lines of:"Initial Catalog=<your database name>;Data Source=<name of the server>\<name of your instance>;Integrated Security=SSPI"There's also some configuring that you'll need to do depending on the firewall setup of the machine you install to. You'll need to enable port exceptions for UDP port 1434 and a random TCP port number. To discover which TCP port use svrnetcn.exe. (only really an issue if Windows Firewall is enabled).There's also a whole lot of other configuring you'll need to do manually... Have fun!Hope this helps!Cheers,Peter MaugerSenior Software EngineerGlobal iQ |
 |
|
|
stephenbaer
Yak Posting Veteran
71 Posts |
Posted - 2006-08-12 : 09:32:13
|
Originally posted by peter_mauger
Ok, if you are worried about effecting the existing MSDE engine then you should absolutely go for a new instance. MSDE can be installed free of charge so there is no worries about cost (there is a limit to the number of instances that you can install... I think 8 is the max). To install a new instance open up the setup.ini file in the folder that your MSDE setup.exe is located.Change the contents to look something like:[Options]INSTANCENAME="<the name that you want to give your instance>"SAPWD="<your sa password for this instance... ideally the same as the other instance>"DISABLENETWORKPROTOCOLS=0 <this allows access from other computers on the network. If the application is only going to be run from the local computer then leave this line out>SECURITYMODE=SQL <this will give you mixed mode access. Leave this line out if you only want to use NT logins. Note that your sa password won't work if you use NT logins only (because it's an SQL login)>
Great, thanks. quote:
If that's a little confusing then go to http://www.codeproject.com/database/ConfigureMSDE.asp and everything will be explained.In your code you'll need to use a connection string along the lines of:"Initial Catalog=<your database name>;Data Source=<name of the server>\<name of your instance>;Integrated Security=SSPI"
In the <name of the server> part, does the domain need to be specified? We'll be using SBS2003. Also, we've decided to move the timeclock app to another machine, just to be safe. It has such a small footprint, it will run on a $299 Dell special.quote:
There's also some configuring that you'll need to do depending on the firewall setup of the machine you install to. You'll need to enable port exceptions for UDP port 1434 and a random TCP port number. To discover which TCP port use svrnetcn.exe. (only really an issue if Windows Firewall is enabled).
We have an external firewall in the router. I assume that whatever information on ports is provided with servernetcn will need to be configured on the router/firewall?quote:
There's also a whole lot of other configuring you'll need to do manually... Have fun![/quote]I'm having a bit of fun, which is always a good thing when you do 100 hours of work for practically nothing. I consider it an educational experience. |
|
|
|
|
|
|
|
|
Multiple Instances of MSDE?