SQL Database as a web backend

[Natraj]

Hi,<br>
I am developing a web application that requires to have an SQL Server 7.0 database as the backend. The database is to be remotely updated every fortnight. The solution that i have arrived at are as follows :<br>
1. Create a temporaty database for the updates and FTP it to my web server<br>
2. Do remote update to my web server via SQL Server.<br>
the updates can vary from few records to thousands of records depending upon sales. Does anyone have any suggestion as which would be ideal of the above or any other solution which i can use.<br>
Thankx<br>
Natraj

 

[Guest_imported]

Both of these seem to be viable means to the end. However, on 2. I am not sure what you mean. I would think the opposite, write some web code to allow you to do a remote update to your database via the web. IS that what you mean? If so, it would be (IMHO) the best route, and I have implemented such s sceme in the past, whereas all I have to do it tyoe the web address and folder, click on the update button, and let my code do all the work. The code isn't too hard to write either.

 

[nitram]

In general you may want to look at the DTS (Data Transformation Service) features of SQL Server.<br>
This will allow the import of many formats<br>
(eg. csv, excel, access db) into a SQL server table.<br>
<br>
Perhaps what you could do is ftp your input files to<br>
somewhere accessible by SQL server and let it pick up<br>
the new data via a scheduled DTS task ? <br>
<br>
Indeed since the DTS wizard generates code to do this<br>
you could also do some amount of data manipulation (eg.<br>
formating, capitalisation, etc) too.<br>
<br>
Site Server commerce edition also has 'pipelines' which can offer similar functionality, if it is available to you.<br>
In fact, you can plug in SMTP, XML and others in place of FTP.<br>
<br>
---------------------------------------------------------------<br>
Computer illiteracy is: thinking cut & paste is a cheap haircut<br>
Company Net, Research Park North Ricarton Edinburgh, Scotland<br>
Email Martin.Ramsay@company-net.co.uk - Tel:+44 (0)131 559 7500

 

[Guest_imported]

nitram,<br>
<br>
Excellent suggestion. I think I may revert to this method, as well. Never even thought about using the DTS. Thanks!<br>
<br>
<br>
John Vogel

 

[calahans]

The first method seems over the top, if i read your idea correctly you are going to ftp a database from one SQL Server installation to another? I would not suggest doing this as it would cost too much time, and probably be a headache.<br>
<br>
I would agree that you could use the DTS Wizard, or if your web link only uses one or two tables why not use BCP, BCP has a normal transfer rate in the thousand per sec.<br>
<br>
Finanly, if your WEB server is on the same network as the server you are getting the info from, why not set them up as a publisher/subscriber relationship and set the sychronise time to bimonthly. This method allows you to scale up your web link if you want to publish other info from your server.<br>
<br>
All the best<br>
<br>
C