Reply to thread

Message: <blockquote data-quote="fox_fsvlfs" data-source="post: 693190" data-attributes="member: 109224">I apologize for reviving such and old thread, but I just wanted to share my opinion. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />I wish that MediaPortal could use embedded database like MS SQL Compact Edition. Why? Because full sql server eats too much resources and managing it can be too much hassle. Why not use sql ce?- it supports 256 concurrent connections which should be more than enough for different modules accessing database at the same time- a need to store relatively small amount of data (like EPG) on TV service side should not be (in my opinion) the reason to use full SQL server, especially if there is a goal to make MediaPortal as mainstream as possible.- multiple clients are still possible (they connect to TV service instead of directly to database) - about reinventing the wheel for communication layer... there is already TV Service that must have some sort of communication layer and if that is not robust enough there is for example WCF (so there is no need to reinvent the wheel). The point I am trying to make is that clients directly accessing SQL Server is not an only option (it is often even not recommended).  Here are what I think are pros and cons of using sql ce:Pros- Make MediaPortal less bloated- Simpler installation- Removes dependency on external module (improperly configured SQL server can lead to compatibility issues, security issues... most end users are probably not qualified to properly configure and maintain SQL server)  Cons- Rewriting part of application that already works is something I can't really imagine anyone looking forward doing- Use of less powerful database engine (but does MediaPortal really needs more?)My experience with MediaPortal:I recommended to friend to try MediaPortal. In the middle of installation, when he saw that SQL server needs to be installed, he canceled installation. He was unwilling to install SQL server on his PC just to try software for watching/recording TV. I didn't argue with him. You know what they say, the user is always right.When I was installing MediaPortal on my system I had MS SQL Express already installed, but I had to download almost 200 MB big installation for MS SQL Management Studio (and install and update it) to enable SQL Server Authentication. I am sure there must be other methods, but that was the only one I knew right off the top of my head. This is just one random issue that external dependencies can bring.  Just my 2 cents</blockquote>

Verification