Where is your database currently deployed? location, format, and size will play a key role in formulating my deployment suggestion.
How does your application connect to the database currently? Windows or SQL authentication?
How many logins are associated with the current database?
To deploy a database from development into production is one thing. To improve that database and redeploy is another. This is the number one fear of customers in the post delivery maintenance phase of application development, whether or not their old data will be compatible with the new version. While it may be easier for you, the developer, to simply introduce a new 'clean' version unencombered by antiquated code or table design, I feel the developer has a responsibility to clients that entrusted their data to your data system to create an upgrade/import/conversion process to bring as much old data forward to the new version as possible. Beyond the personal ecconomic benefits of not alienating your clientbase with every new version, future developers will benefit from users with good technology experiences.