A Book......

Hi,

Does anyone of you perhaps know of a book that will teach me how to upload and maintain a sql server db to my website.

I have a web using asp and sql server which works fine on my pc running IIS and NT SERVER, but I do not know how to upload and maintain this on the web.

Thanks,
T

Unless you are your own ISP this is going to be a bit difficult! Your best bet is to talk to your ISP. Not that many of them will run SQL Server on NT with IIS.

NT and SQL Server may well be pre-dominant in the Intra and Extranet worlds but Unix still rules on the Web.

Cheers,

Paul.

I cannot understand this, because wherever you look you see companies advertising NT/SQL SERVER/IIS hosting. As a matter of fact the guys I host with do exactly this - I just do not know how to upload the db.

Thanks anyway Paul

If you can find the hosting, great. You wouldn't upload the db because the ISP would have to give you Admin privileges (and if any ISP is willing to do this, run a mile)

I really would suggest you talk to your ISP, 'cos each one will do it differently. When we did this we had a duplicated Web Server in the office for testing and when we wanted to make changes we had to send the files to the ISP for them to implement.

Cheers,

Paul.

Thanks Paul,

The sending of the files is a problem for me. I have IIS on my pc (ie. I DO have a webserver). Exactly what you did (send the files to the ISP), I now want to do, but HOW??

With access it is easy - ftp the *.mdf files. What files do I upload/ftp when using sql server. Say I have a db names mydb and 2 tables named mytab1 and mytab2... how do I upload these files. What will mytab1 and mytab2 have as extensions eg in Access I will have a file mydb.mdf and this I will upload!! How is this done is sql server!!!!

Thanks,
T

The database consists of (usually) three files. The primary data (.MDF), secondary data (.NDF) and log files (.LDF). These files can span multiple disks. You can't simply copy the files to the ISP, even if you can identify them and get them there. This is because the master database in the ISP's SQL Server installation would not 'know' about that database. This is why we had a duplicate installation, that way we could copy the files.

I am unsure how you would register your database with the ISP's installation. There may be some sp_... system procedures to do it, but I don't know. I am an analyst and developer, not a DBA:(

Cheers,

Paul.