Hi, we are thinking of installing sql server as a backend to our
website.

Q.1. What is the best way to do this - should we host the database on
the same IIS server where the website is hosted, or would it be better
to put the database on a server on it's own, separate from the IIS
server?

Q.2. Also what is the best way for clients to connect to the database
for querying purposes - will I be able to install client versions of
sql server on their machines so they can connect for querying purposes
only, (cannot create tables etc), or will it be better if the clients
have sql server express installed locally and connect to the server
sql through odbc?

Q.3. When connecting to a sql server database through odbc, using ms
access or sql server express, what happens when queries are run or
updates are made - does the original database on the server get
updated or only the local copy on the client? Also will the client
always have the most recent data?

Sorry, for all the questions, thank you very much for replying. I have
used DB2 in a client server environment but am new to sql server....

What sort of traffic , will you be getting?

q1. You can put the db on the same box as IIS , but if you have separate
boxes , and you
envisage throughput will be significant , then separating them is a good
idea.
Is a RAID array available?
q2. Isn't the website going to be the client end for querying?
If that is the case , then there is no need to have SQL Server Tools or
express installed on the client machines.
They would just use the web front end as the querying mechanism. On the
other hand , if there is a further requirement to
allow developers (for example ) to query the db directly, thn just install
SQL Server express and give them a User who is defined
as only having SELECT permissions

q3. If the main depository is the main SQL db , and you connected via a
client such as SQL Server express , then if you ran
an UPDATE on the main depository and that user had UPDATE permissions then
the main db would be updated

--

Jack Vamvas
___________________________________
Search IT jobs from multiple sources- http://www.ITjobfeed.com/SQL




"Sue" <sea_099 (AT) hotmail (DOT) com> wrote

Sue (sea_099 (AT) hotmail (DOT) com) writes:
Install on a separate box if you can. Else IIS and SQL Server will
compete for memory. There is also a security aspect.

What clients? Didn't you say this was for a web site? Then I would
assume that client connect over the web.

It's difficult to answer this question, without knowing what the
requirements are.

If they update the local database, they update the local database. If
they update the central database, they update the central database. You
can set up replication, to distribute updates, but again, without
knowing what the requirements are for your possible, it's impossible to
give a useful answer.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx