IIS 5.0 w/ SQL Server
- Started
- Last post
- 22 Responses
- nh
I was wondering what tools you need to test for SQL Server on IIS 5.0. I have IIS setup with SQL Server and I'm trying to export an Access Database as a SQL Server Database using the upsizing wizard in Access but it doesn't seem to work.
Would that be the correct thing to use? Do I need a copy of SQL Server? The box that will hold my application when it's finished will have SQL Server but I'm just trying to develop on my box at home right now. Any help or insight would be greatly appreciated.
- mitsu0
sql doesn't have .mdb files like access. what you think you're trying to accomplish isn't possible.
install sql server on your box and then import the data from access.
- unknown0
use enterprise manager for SQL server to import/export databases tables. much much easier than using the upsizing wizard in access.... go to http://www.aspin.com and search for tutorials on sql server.. im sure they have a couple linked there
- nh0
http://www.aspin.com/func/conten…
Does this look like something that would work?
Since I have IIS 5.0 installed and all of the MSDE stuff, I should be able to test once I get a SQL Server DB right? Or am I completely mistaken. Thanks so much and sorry for the newbie questions.
- unknown0
it's like mitsu said, you have to have your SQL server set up and able to communicate with your webserver before you can import/export to SQL server. SQL server comes with a handy little program called enterprise manager that you can use to import/export from access/exel or a bunch of other types of dbases.
- nh0
So then I am completely mistaken in believing that I can test for SQL Server without actually owning a copy of it?
I am building an intranet that will not face the internet and the client's parent company will not allow their copy of SQL Server to touch the hands of the client, let alone me.
Is there anything I can do to test?
Sorry, I am fairly new to this and have never worked with SQLServer before.
- unknown0
you could connect to their SQL server remotely... SQL server isn't like Access at all, it doesn't produce files per say, it is a data storage application that acts as a server, in much the same way IIS is an application that acts as a server.
- sparker0
you should ask for a couple thousand dollars as an expense to the client and buy a copy. if they want the work done, and done right too match their system they need to pony up all available systems and environments.
you don't ask a contractor to build a house without giving him land.
tell them to at least set up a test box at their office for you to terminal/remote into so you can test the development.
but, i have to ask, why are you working on this at all? if you don't have the experience with large scale rdbms then hire or co-opt with someone that does. not only will project be more successful but it will go easier and quicker for you.
- unknown0
have to agree with sparker on this one.... there are plenty of head in here that have SQL server experience... I'd farm out part of it if I were you.
- nh0
When I got into the project I didn't know much about coding at all but I have now read a few books and have a few friends I have been able to speak to. The client's parent company wants to convert everything from Access to SQL Server at the last minute. They don't want anyone touching their software, they are very protective and will compromise the project to keep people away.
I really didn't want to do the project like that. I would rather try and test against SQL Server and I was just trying to figure out a way that I could do it. No I'm not a programmer but I'm learning and the application is turning out very well in my opinion. I just don't know much about the db technology.
If anyone knows what I am looking for, or an answer that will slap me across the face please give it. No one is buying me SQL Server and they won't let me connect to their network unless I work inhouse at their offices and that is not an option.
- unknown0
is SQL server an option where you host your website? If it is, I'd get setup on it. my website is ran off of an SQL server and the SQL server is only like 25$ a year extra.... then you could test using it. just a thought. thats all you're really going to be able to do, unless you farm the work out to someone that has access to an SQL server. Most people won't give you access to their SQL if you don't work full time for them.
- sparker0
then there isn't a way to do it. sql server 2000 is a ms specific system. it's not like oracle or db2 where there are open-source tools and options readily available...
you might hunt around freshmeat.net or sourceforge.net and see if there are any...
tell them, it is a must to have access to the system or a test environment.
you MUST have the server in order to do this.
if you anticipating any more projects like this in the future, it would be wise to buy it. it's right around 2K for the server software....
you may want to build or buy a windows server as well...we recently set up an exchange server because a client needed one set up...we made up the expense with the project cost though. so, it wasn't that bad.
- mitsu0
this is silly. dude, you need to outsource that backend work to someone with a few years of db experience.
the reasons are too many and too obvious to list.
- nh0
thanks, maybe I'll look around for a host.
- nh0
the db is already set up. I just don't have access to it.
- sparker0
but there is more to it than that. the server might be set up, but if the company just decided to switch from access to sql, then i doubt they've got all the necessary configs set and probably none of the dbs set up.
have you seen their db infrastructure yet? is it ready to go, or are they actually expecting you to handle this too?
- nh0
The DB is completely set up. I have a toned down Access version of it that I created based on the structure that they have requested.
I just don't want there to be any problems when these people get ahold of my code. They are db engineers and supposedly don't know much about code so I wanted to hand it to them working. From what I can tell the only difference would be in my connection strings but I wanted to be able to test the correct way to make sure of that.
- unknown0
well, if they have database engineers, they should be able to set upa user on their SQL server that would only have access to said database as a datareader and a datawriter. then they would just have to give you an IP address, login, and password. From there you could use the upsizer thingy in access to publish the tables and do your testing. Like mitsu said though, if you're this much a newbie on this stuff it would probably be good to seek outside assistance on this project. it sounds like you need to talk to their dbase guys too.
- nh0
I've got good communication with the db guys. They are part of the parent company and don't give a rats ass about the development of this project. We are having to play around with them to even get it on their servers when it's finished, and they won't allow the client to put it on their own server, I'm not sure why but what they say goes and so that's just how it is. I guess if the remote way is the only way it will work that's not going to happen because they have already stated that.
Can anyone then confirm how difficult it is to change the code that is used to access an Access database into code for Accessing a SQL Server database.
Sorry I'm such a retard, I'm a bit out of my element on this one and the people around me are making a valid effort to make this difficult on all parties involved.
- mitsu0
have them set up a dsn on the web server and change your open method to this:
oconn.open "dsn", "user", "pwd"
put your connection code in a server-side include incase they ever want to change anything last minute. it's hard to say your insert, update and delete code will transfer properly, but i don't think you'll have a problem.
- nh0
Thanks for the info on the conversions.
As far as web servers go, they don't have any servers facing the web.