Friday, February 11, 2005
« New .Text Skins | Main | Addicted to E-mail »

The most frequent question I'm asked about hosting at ChristianASP.NET is database support.  I love Microsoft SQL Server and have used it for years.  (Since version 4.2!)  Obviously, I can't afford what it would take to license SQL Server in a hosted environment.  I have a few users who are using Access or MSDE.  I know that MySQL and PostgreSQL may be viable solutions, but I've never used them.  I know absolutely nothing about setting them up, or hosting them so that they would be secure and properly maintained. 

Anyone have experience with either MySQL or PostgreSQL?  Any advice or resources you'd recommend?

Friday, February 11, 2005 8:43:00 AM (Central Standard Time, UTC-06:00)  #    Disclaimer  |  Comments [4]  | 
Tuesday, May 17, 2005 5:19:00 PM (Central Standard Time, UTC-06:00)
I believe that any DataLayer must be a simple code block, that they allow operations against DB.



That code block would not have to know on the Business Entities. Single to specialize it is to execute the operations (Store Procedures and SQL Sentences) against the engine DB (SQL, Oracle, DB2, etc.), with which this setting.



Finally, I invite to you to download the DataLayer.Primitives Public Version.



This is very cool Data Layer :)



DataLayer.Primitives - Readme!

http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=1389



Cheers,



Javier Luna

http://guydotnetxmlwebservices.blogspot.com/
Friday, February 11, 2005 12:11:00 PM (Central Standard Time, UTC-06:00)
I was already aware of MySQL not supporting stored procedures (yet). This isn't necessarily for me, but something I can offer as part of my free web hosting deal. My immediate concern is setting up MySQL for anyone who wants to use it, and configure it so it's secure and maintained properly.



However, I am thinking about using MySQL on a personal project, and the lack of stored procedures isn't concerning me that much. The reason is I've also been playing around with Paul Wilson's ORMapper (www.ormapper.net). I would like to rewrite the data layer of my portal framework (which is currently 100% stored procedures) so that it can run on top of "any" database. My biggest concern right now is how to implement my role-based security, which currently has some pretty heavy-lifting stored procedures and UDFs associated with it.
Friday, February 11, 2005 10:54:00 AM (Central Standard Time, UTC-06:00)
Yeah, MySQL is good if you need something free. But like Yex mentioned above, v4.x doesn't support SProcs. I believe 5.x is planned to have this.



As far as scalability, I know of a few very large apps that use MySQL very successfully so it seems to be able to scale pretty well. But I'm still a MS SQL guy myself because of the SProcs. Perhaps when MySQL v5.x is out I may look at using it more.
Friday, February 11, 2005 9:46:00 AM (Central Standard Time, UTC-06:00)
Yeah, I've used MySQL quite a bit, and it's actually a pretty decent database depending on the scale of the application you're dealing with. For relatively small applications and userbase, MySQL runs great, and it easy to maintain. MySQL has released a provider for ADO.NET on their web site (http://www.mysql.com), so it can be used fairly well with ASP.NET applications. It's also got some great management tools on their web site as well. So overall, I'd recommend supporting that as a host. The only real drawback to MySQL at this point is it's lack of support for stored procs, which is coming in a future version, but I'd imagine that's still a ways off though. It's definitely planned, but it's not there right now. Other than it's relative lack of scaleability (yeah, that's probably debatable too if you were talking to a hardcore MySQL guy, which I am not) that's pretty much it's only drawback that I know of right now. Other than that it's really nice.



Postgresql is another story. I've heard great things about it, but it's pretty much restricted to the *nix platform. I understand that it *can* run on Win32 if you run it over Cygwin, but that's just a pain in the butt, and I'm not sure it's worth the trouble.
Comments are closed.