# PostgreSQL or MySQL **URL:** \ **Category:** Archived Topics\ **Created:** [August 20, 2007, 2:37am UTC](https://forum.inductiveautomation.com/t/postgresql-or-mysql/341 "2007-08-20T02:37:36Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jdelgado](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jdelgado](https://forum.inductiveautomation.com/u/jdelgado)\ **Post date:** [August 20, 2007, 2:37am UTC](https://forum.inductiveautomation.com/t/postgresql-or-mysql/341/1 "2007-08-20T02:37:36Z")
I know this is a broad topic and not specific to FactorySQL, but any users our there that have used both. Any recomendation ? I have been using MS-SQL and we are thinking of given one of the open source a chance. which one will have better support in .NET using strong typed datasets. Which one will perform faster ? More robust ? Any preference on the FactorySQL community or company? Thanks jdelgado ---
**Author:** ![nathan](https://avatars.discourse-cdn.com/v4/letter/n/c5a1d2/32.png) [@nathan](https://forum.inductiveautomation.com/u/nathan)\ **Post date:** [August 20, 2007, 3:42am UTC](https://forum.inductiveautomation.com/t/postgresql-or-mysql/341/2 "2007-08-20T03:42:11Z")
We now recommend MySQL over PostgreSQL. Microsoft SQL Server is a great program as well. All 3 platforms are robust. SQL Server surprised me and actually ran the fastest, but they all can push pretty high data rates. Stay tuned for exact benchmarks with SQLTags (Early October). I would have to say that MS SQL Server would have better .NET support for strong typed datasets. A quick google search yielded that you can create [ADO.NET](http://ADO.NET) strongly typed objects that allow you to deal with dataSets like regular objects to avoid referring to them by index alone. A similar search indicated that this appears to be possible with MySQL using your own XML based definitions. That said, I know very little about this area and I’m unclear on how this relates to FactorySQL unless you’re writing a custom .NET plugin. I personally like working with MySQL. I’d give that a shot and see what you think. ---
**Author:** ![jdelgado](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jdelgado](https://forum.inductiveautomation.com/u/jdelgado)\ **Post date:** [August 20, 2007, 1:22pm UTC](https://forum.inductiveautomation.com/t/postgresql-or-mysql/341/3 "2007-08-20T13:22:14Z")
Thanks nathan. ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [August 20, 2007, 4:20pm UTC](https://forum.inductiveautomation.com/t/postgresql-or-mysql/341/4 "2007-08-20T16:20:06Z")
For what its worth - we used to recommend PostgreSQL, but switched to MySQL because of PostgreSQL’s poor performance and reliability on Windows. ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [August 20, 2007, 4:41pm UTC](https://forum.inductiveautomation.com/t/postgresql-or-mysql/341/5 "2007-08-20T16:41:39Z")
And since you asked about programming in .net, I’ll throw in that, at least in my experience, the MS-SQL connector is much better than any connector available for the other dbs. Of course the others work, and we’ve been able to obtain very good results across all 3 platforms, but whereas the SQL Server connector is a full part of the .Net framework, the mysql & postgres connectors are simply side projects, and definitely can show it some times. Honestly, unless there’s some good financial reason pushing your desire to switch, I’d stick with MSSQL. Then I’d recommend mysql. Hope that helps, ---
**Author:** ![jdelgado](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jdelgado](https://forum.inductiveautomation.com/u/jdelgado)\ **Post date:** [August 21, 2007, 11:32am UTC](https://forum.inductiveautomation.com/t/postgresql-or-mysql/341/6 "2007-08-21T11:32:08Z")
thank you guys