Best way to create a database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi;

We have an ASP.NET portal product we are about to start shipping. It needs a
database to run. To create the database which approach do you recomend (and
why):

1) Provide Erwin generated scripts for each vendor that will create the
database. Require person installing to apply the script to their database.

2) Make ADO.NET calls to create the database. Have this as part of the
install program and prompt them for server, database name (that we create),
uname, & password.

3) other???

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm
 
Why not both?

Let the Administrator have the option of manually running the scripts
if the Admin is very confident of their SQL knowledge, or they can run
with ADO during configuration, which would probably work with 90% of
SQL engines out there.
 
Hi Dave

First of all, I¡¯d like to confirm my understanding of this issue.
According to your description, you want to know which approach is best to
create a database.
If I misunderstood anything here, please don¡¯t hesitate to correct me.

Have you considered using both?
You can use ADO.net during configuration.
It could prevent admin running the scripts to create a database.
so admin may only click ¡°install.exe¡± to create the whole database
without manually running the scripts, I think this is more friendly.

Also, allow the Administrator the option of manually running the script
when the ¡°install.exe¡± isn¡¯t working.

Hope this helps and if anything is unclear, please let me know.

Wen Yuan
Microsoft Online Community Support
===============================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
===============================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Ah, I would NOT assume that more than one DBMS SQL engine supports the same
DDL calls to create databases. While these might be very similar for
Sybase/Microsoft SQL Server, I would not count on them working for Oracle
and they won't work for JET/Access or SQL Server Everywhere. I suspect that
each database will have its own DDL.

Okay, so you've created a database--what about the tables, datatypes, PKs,
indexes, FKs, rules, triggers, procedures, views and everything else? What
about the data?

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
 
Hi Dave

Yes, if you have many vendors (each vendor with his own version).
It's not easy to create so many databases and distribute for each vendor.
So, in my opinion, you can do it with ADO.net to create each database on
each vendor's server.

If there is anything I can help you with, please let me know.

Wen Yuan
Microsoft Online Community Support
===============================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
===============================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
That doesn't sound like fun, trying to support so many DB's out there.
If I were you, you might consider supporting the Top 5 DB systems that
are typically used by the kind of software package you are selling
(retail website, accounting systems, forums, etc)

I'll admit, my experience in marking an in-house software package to
the masses is not something I've ever done, though. :)
 
Back
Top