| Author |
Topic |
|
ryanoc
Starting Member
25 Posts |
 Posted - 2007-07-18 : 13:42:26
|
| I'm creating a new database for an application that I wish to sell in the future. When we sell it the client will have the option to host is or have us host it. I want to create a name for the database that doesn't describe what the product is. I also want to be able to create new databases if we host it and those names be of a similar convention or subject. I was thinking each would be a Greek god, galaxy names or something along those lines. Does anyone have any suggestions?Thanks,Ryan |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-07-18 : 13:53:49
|
| Why not setup your application so it will work with any database name, and let the client chose the db name?CODO ERGO SUM |
 |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-07-18 : 13:56:18
|
| moved from Site related discussions forum_______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-07-18 : 13:58:30
|
| I don't agree with using cute database names. Database names should be descriptive. How else are you going to remember which database is for which client on the system that you host?For databases that the client hosts, the database name should include the product name.For databases that you host, the database name should include the product name and the client's name or some other identification, such as ProductName_ClientName.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-07-18 : 14:02:20
|
if you want unique just give a guid name to every db  i agree with tara though._______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
|
|
|
ryanoc
Starting Member
25 Posts |
Posted - 2007-07-18 : 14:03:35
|
| Yeah, the cute names are probably not the greatest idea. The product is evolving. It started out as a CRM, but is moving into different territory. I just don't want be stuck with a name that boxes me into something that Ive grown out of. We don't have a a company name either. |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-07-18 : 15:33:36
|
| I think you need to allow your application to use any valid database name. If you don't, what will you do if your customer already has a database with the same name you have chosen? Tell them to buy a new server?What if you need to run more than one instance of the application on the same server? This is especially important for development, QA, and hosting.Also, don't box yourself in by insisting that they connect to the server with a particular login, and make sure it supports both Windows and SQL Server logins. And make sure that your application does not require the use of sysadmin logins or has to be dbo in the database. If you don't, your customers DBA's will hate you from the beginning (with good reason), and they may be very influential in the buying decision. Nothing says "designed by clueless amateurs" better than poor database security design in a vendor application.CODO ERGO SUM |
|
|
|
thewebhostingdir
Starting Member
3 Posts |
Posted - 2007-07-20 : 00:24:04
|
| Ryan,You need to allow user to keep database name of their choice. Consider this scenario ...Your two customers are hosting their sites with common host. Both have been offered the same SQL Server to host their database... now any one of them will be able to host your application due to naming limitation...:)Jason P.AccuWebHosting.ComSQL 2005/2008 Web Hosting |
|
|
|
|
SQL database naming