|
-
Oct 17th, 2023, 03:41 PM
#1
Thread Starter
Fanatic Member
[RESOLVED] Where should the database go?
Publishing/distributing an application truly confusing and complex. I am sure it is not supposed to be, but it is. I have finally gotten through the basics and, most of the time, successfully carry out this process. However, there are a couple of things I am wondering about, with regard to publishing/distributing a database application.
My applications are pretty simple and while they require a database, they do not require, nor are they well served, using a server-based database. It has been my practice to include the database as part of the package that I publish to load on another machine. However, I am beginning to see problems with that approach and am now considering that I might be better served to publish/distribute the application without including the database in the package and installing the database separately to the specific place called for in the application connection string.
I am just looking for pros and cons as to what would make a better approach.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|