How to handle a BO for different database?


Author
Message
Edhy Rijo
E
StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)
Group: StrataFrame Users
Posts: 2.4K, Visits: 23K
I don't know if this is possible or not with the BO, but I need to design an application that can be used with different database like VistaDB and MS-SQL.



The idea is that there will be customers that will use VistaDB mostly for single users and others will use MS-SQL for multiple users. Can a BO be setup to connect to either database? How?



P.S.

My understanding is that VistaDB database is pretty much compatible with MS-SQL TSQL language, they do not support all the features of MS-SQL of course, but at least it looks like they support all the standard features and if that is the case, then it may work for my project.

Edhy Rijo

Reply
Edhy Rijo
E
StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)StrataFrame VIP (6.4K reputation)
Group: StrataFrame Users
Posts: 2.4K, Visits: 23K
Dustin Taylor (04/20/2010)
Charles is right on (seems like I've been saying that a lot lately w00t )


Agree, Charles is just getting better and better. Hehe



Your BOs should be no problem at all. As Greg mentioned, you will just be dealing with your DataSourceKey, the BO logic shouldn't be affected, especially if you write your Queries to be compatible with both MS-SQL and VistaDB from the get-go.


Good to know will test that next week.





The DDT, however,will not be able to deploy to VistaDB, and the RBS would be sketchy at best.

The best option for your VistaDB boxes may be to put RBS on it's own SQLExpress instance. That way you don't have to worry about compatibility, and the RBS won't hit any size limits like you may run into with your main APP database. If you did take that approach, I would probably go ahead and seperate out your RBS tables into a seperate DB for all of your installations, regardless of whether they use VistaDB or MS-SQL. That way, you don't have to account for anything fancy on the security side of things, it will always be it's own DataSourceKey, which you set up once and, afterwhich, can rely on. If you end up running into performance issues by having two connections to the same DB open for each MS-SQL client, we can re-evaluate that, but I think I'd design it simple up front, and then only add extra complication if it proves necessary after testing.



From there, the only thing you have to account for is deploying your VistaDB, and keeping track of which datasource to use for your BOs (which wouldn't be terribly hard to account for using an inherited BaseBO.)




I understand and that is the reason we are asking you guys to add support for those databases or at least some sort of open source hook where we can make the tools works with other database. In my case, it will be impossible to install MS-SQL express on some customer computers, SQL-Express setup will not even install and unfortunately for this application that is the majority of customers, some customers have decent hardware with one or more branch office, for those MS-SQL Express will work just fine.



About RBS I hope the structure and logic used in SF could be use in VistaDB, so after testing I will let you guys know what i find. Hopefully the overhaul being done to the DDT will have some open architecture to allow us to expand the tools and be able to use it with any database with our customization if needed.




Edhy Rijo

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search