Folder for database

[Jim McGivney]

Due to cost constraints I have decided to use an Access database from my
ASP.net project.
I will use an OleDBConncetion.
I am using VisualStudio.net 2003.
While I work on this project on my development computer, where should I
place the Access database ?
Should I place it in the appropriate VisualStudioProjects folder or should I
place it in the appropriate folder in C:/inetpub/wwwroot , or somewhere else
?
Thanks in advance for your help.
Jim

 

[Curt]

1) Is security an issue? If so, I suggest storing the database in a
different folder where IIS and it's delegates have no rights. Allow access
only through the application.
2) Will other applications need to access this database? If so, a central
location, not specific to any of the accessing applications is the right
choice.
3) If the first two answers are no, then it might be acceptable to place
the database in the project folder.

Regardless of the location, you should create dynamic connection strings so
you can easily move the database if and when necessary.

Good luck,
Curt

 

[shiv_koirala]

Keep in a folder which is not mapped to IIS... So do not keep it in
wwwroot.

Shivprasad Koirala
C# , VB.NET , SQL SERVER , ASP.NET Interview Questions
http://www.geocities.com/dotnetinterviews/

 

[shiv_koirala]

Sorry just forgot something why do you try MSDE better than
access......Just a suggestion


Shivprasad Koirala
C# , VB.NET , SQL SERVER , ASP.NET Interview Questions
http://www.geocities.com/dotnetinterviews/

 

[John Rivers]

Use MSDE - its a free version of SQL Server

completely binary compatible - you can even install the client tools

from SQL Server and they work with MSDE perfectly

 

[tom pester]

You should definitely place it in a directory somewhere else so that the
visitor can't download the database.
If a user tries www.yoursite.com/db/project.mdb after guessing (or hacking)
he will get the access database just like any other file.

If you develop with the connection string in an Application variable, like
Application("connStr"), you can easily change the location of the database
or underlying product (migrating from access to sql server isn't difficult).

If you use access you will find some situations where it doesn't scale:
- When 5-10 people are concurrently doing write activities to the db
- In my experience the access file gets corrupt every few months if it's
under stress

Access is a nice environment to develop in. If you need robust power and
already do know databases its better to work with the free products MSDE
or SQL Express.
The former missed a good graphical interface but that's solved now with SQL
Express.

HTH

Cheers,
Tom Pester

 

[Jim McGivney]

My hosp doesn't charge an additional fee for an Access Database, while it's
$9.95/Month for SQL server, necessary to use SQL Database even with MSDE.