Having to support an older VB.Net application, I get performance issues when several workstations are working with the MySQL database via ODBC at the same time. I'm now thinking about switching from ODBC to the MySQL Connector/NET.
I don't know Connector/NET at all. Does anybody have experiences with a switch like this? Are there any caveats? Is it even worthwile? Would it be a lot of work (the app relies heavily on MySQL)? I didn't find anything about the efford needed. Any thoughts? Thanks.
Related
I was looking around for some solution to bring TDE to MySQL. I found this question asked in here before.
But the question seems to be about enabling a TDE solution to a MySQL database that is installed in a Linux environment.
In my case, I would need a TDE solution for MySQL that is installed in a Windows Server 2008 R2 environment.
I have found NetLib and it seems to be working for me. Question is, are there any other alternatives? Also, is NetLib good?
EDIT:
So now using TrueCrypt with MySQL is possible. But, is there any other alternative to this? One that has been audited perhaps?
MySQL doesn't care what solution you're using as long as you provide it a filesystem that acts like a filesystem. It deals only at the file level. Do understand that performance may be severely impacted, however.
I'm planning a new sistem which is going to use quite large datatables. I'm not sure about which database I ought to use: FireBird (v. 2.5) or SQL Server Express (v. 2008). Despite the limitations of the Express version of SQL, it seems to be more integrated with .NET. Otherwise, FB must to connect with .NET through an "not included" ODBC driver, and I dont' know if it would reduce performance. Anyway, FB seems to be more robust, reliable and not limited as a free version of SQLS. What should I know about this comparation?
As others said: for Firebird, you don't need to use an ODBC driver; there's a native .Net driver which is actively developed/maintained. See the main Firebird site
Additionally, there's a DDX module that lets you integrate Firebird into the Visual Studio (all editions except Express) GUI (database connections etc)
Firebird pros:
- no conscious built in limits/throttling. SQL Express apparently is limited to 1 GB and 1 physical processor Wikipedia but I'm sure there's tons of MS documentation
- scale out from local (embedded or listening on 127.0.0.1:3050) to separate Linux or Windows database server if your dbs get really big
- active support community, paid support available
- allows easy switchover to a Linux/Unix application/environment
Firebird cons:
- SQL Server is more mainstream with .Net (more examples, tighter integration)
- if you're not used to it you have to learn it. Applies to SQL Server as well, of course.
My opinion: if you're willing to learn, go with Firebird and make sure you properly tune the database, possibly with help from the Firebird mailing list (quite helpful).
If you want the easy (from an app dev point of view), mainstream .Net, possibly more expensive way, go with SQL Server Express and scale out to regular SQL Server.
Note: I do not have experience with large scale SQL Server or FB databases, just a happy Firebird user.
Is there a way to communicate these Platforms effieciently?
I'm saying, something like exporting (SQL Server)and load (Matlab) but in an efficient way?
I've found adodb_tools on File Exchange to work the best so far. It's much faster than the database toolbox or any prior wrapping solutions.
Doesn't require additional toolboxes but in all likelihood will require you're on Windows for the ADO OLEDB ActiveX support.
Use MATLAB's capability to run Java code in order to access any database that provides a JDBC driver. If you mind using Java, buy the Database Toolbox as mentioned by #b3.
As mentioned use Java and the JDBC driver for your chosen database.
If you look through Stackoverflow there are a few posting about connecting MATLAB and MySQL.
MySQL and Matlab
and
How can i remotely connect ODBC using Java in Windows XP?
These solutions should work with a little tweaking for your database driver.
We have just moved our high volume ASP classic website from Windows server 2003, 32bit, iis6, Mysql to server 2008, 64bit, IIS7.
We are experiance some truncated data and page slow downs on some pages that make a lot of calls on the DB. We are using ODBC Driver 3.51.
We are pretty sure it is the ODBC driver but have no idea how to fix it
Any ideas
Thanks in advance.
The answer is simple. Many of the sql queries on the site are handled badly by ODBC Driver 3.51.
Slowness and truncation of data being some of the obvious problems and can often be fixed by rewriting the way loops through data can be handled. Handling a lot of processing in memory has also helped.
We are going to test a newer version of ODBC client soon to see if that is faster and more stable.
What is the best component to use when connecting to a Mysql 5.1.x in Delphi and why ?
No other DB components could beat DevArt DB Components, they have MyDac and UniDac, both of them could use direct access to the database without requiring mysql client to be installed on the client machine, beside they offer fast performance and high quality compared to other components
Data Access Components for MySQL
Universal Data Access Components
and check the pages above to know why ;-)
You should take a look at AnyDAC, supports MySQL and a lot of other databases.
Devart and microOLAP both offer components to access MySQL databases. Devart also have dbExpress drivers for dbExpress users.
Bob Swart has published Delphi for Win32 VCL Database Development on Lulu, if you need any help.
Don't forget that MySQL's client dll are GPL-ed, and if you are using it to connect to server, your app must be GPL-ed.
There are alternatives. Components that connect directly to MySQL skipping GPLed dlls. DevArt has such components (direct and dbx), and there are free components that can connect directily on tory.net.
I don't use MySQL, but when I can, I prefer dbExpress. It's unidirectional, which makes it pretty fast. Though I haven't done any benchmarking recently.
If dbExpress isn't your thing, I found this list of components for MySQL access.