March 10, 2014 at 10:27 pm
Comments posted to this topic are about the item SaaS and Multi-tenancy Models
[font="Tahoma"]Cheers,
Sean :-D[/font]
March 11, 2014 at 1:56 am
can anyone explain "data warehouse" vs "enterprise data warehouse" ?
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
March 11, 2014 at 2:02 am
Option 1 & 2:
Depending on the application does allow the Client the freedom of upgrading when they want. When you get to a professional application for a complex area then this is really the only option. You still get certain efficiencies of scale, a bit more admin which can be handled by scripts.
Option 3:
If there are a lot of stored procedures then it does rely on database developers being on the project. Currently I have 2 inexperience developers mucking around and it does cause more grief. Also, this option is great if you have the arrogant attitude of saying to your clients this is when you will be upgraded whether you like it or not!
March 11, 2014 at 12:15 pm
We're pretty much on Option #3 as you described them. We use SQL Projects to handle the code changes and they usually aren't too bad, but trying to do customized reporting or SSAS is definitely a challenge in that model. Doable, but not easy.
I'd like to hear more about the details behind how you've implemented Option #4, perhaps in a future article. I'm not quite sure I followed the common staging area concept completely.
March 11, 2014 at 1:19 pm
Peter,
We have 2 more articles in the series done and in the publishing queue at SSC. We have planned 5 articles to cover most of our implementation highlights. One of them is around reporting/analytics security in SSRS/SSAS which will be relevant to your area of interest. So keep tuned!
Thanks,
Sean
[font="Tahoma"]Cheers,
Sean :-D[/font]
March 13, 2014 at 10:12 am
5th Option - Use a RAM Centric Model in a JVM
Build your database in RAM on your system in a JVM. Store all leave objects changes (edit/insert/deletions) immediately to disk (encrypt your disk). Add a new tenant, build a jvm. Build a customized front end to access the system via https to support live clients and system services. Three layers in all.
April 22, 2014 at 10:40 am
Thanks for the article. I especially appreciate the Information Maturity Model graphic. What is the source of that? I find it to be very insightful.
FYI, I posted a message under the topic of "A Different Hybrid Option" that describes our approach to the challenge you outlined.
April 22, 2014 at 12:19 pm
It has taken on different forms internally over the years. The best I know its internally sourced from my employer's staff from ICF.
[font="Tahoma"]Cheers,
Sean :-D[/font]
June 22, 2021 at 6:41 am
This was removed by the editor as SPAM
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply