jarrette wrote on Tuesday, September 22, 2009:
Hey guys, I’m very interested in getting the database file separately as my first step in converting this project for our .NET environment. I’d like to convert the HIPAA compliant tables to SQL Server and then get cracking on the code. Is there a way to get the database file by itself?
sunsetsystems wrote on Tuesday, September 22, 2009:
What database file is that?
I’d suggest "extending" rather than "converting" the database interface. I.e. abstract the database layer so it is not specific to MySQL, but still works with it as well as your preferred server and potentially other SQL servers in the future. That way the project will want to include your work and not leave you out in the cold.
This is a nontrivial task, but would be a very nice improvement.
jarrette wrote on Tuesday, September 22, 2009:
I want to get to the schema, get the tables, the actual database itself.
sunsetsystems wrote on Tuesday, September 22, 2009:
That would be sql/database.sql in the distribution.
jarrette wrote on Wednesday, September 23, 2009:
OK, I had the "appliance" and not the actual app, was confusing the hell out of me. Thanks for the help hehe.
bradymiller wrote on Wednesday, September 23, 2009:
hey,
Check out the project website homepage at oemr.org, especially the downloads page, to see explanations of all the packages.
-brady
jarrette wrote on Wednesday, September 23, 2009:
I’ve got the SQL file, now the trick is getting that script to work for SQL Server 2008. Is there a better way then manually going through each create table and rewriting the script.
jarrette wrote on Wednesday, September 23, 2009:
sheesh, I’m new to mysql, i’m using the standard client. It looks like the client removes whitespace so all the comment lines from the database.sql file get mashed into the statements. Going through each statement one by one and copying/pasting into the client. What a pain.
jarrette wrote on Wednesday, September 23, 2009:
OK I downloaded the mysql gui and used the adminstrator to "restore" the sql db, now I’ll just convert the db over to sql server. Sorry for this thread being so annoying 
josephenochs wrote on Wednesday, September 23, 2009:
On the contrary, I’m finding it rather exciting. It will be interesting to see how the mysql functions, triggers, etc… transition to microsoft sql.
jarrette wrote on Wednesday, September 23, 2009:
are all the functions and triggers I will need in the database.sql file?
sunsetsystems wrote on Wednesday, September 23, 2009:
There are no functions or triggers.
bradymiller wrote on Wednesday, September 23, 2009:
hey,
In case you want to support language translations:
The database.sql file contains everything but the language translation tables (three tables); they are empty dummy tables in database.sql. The sql file that contains the filled language translation tables (these are brought in during the installation setup.php script) can be found here:
http://openemr.cvs.sourceforge.net/viewvc/*checkout*/openemr/openemr/contrib/util/language_translations/currentLanguage_utf8.sql?revision=1.11.2.6
-brady
josephenochs wrote on Wednesday, September 23, 2009:
Thanks Rod:
I’m also assuming that there are no stored procedures?
Meaning that all logic other than primary/foriegn key relationships are handled in php code in the web pages…
sunsetsystems wrote on Wednesday, September 23, 2009:
Yes that’s correct. No stored procedures. Even most foreign key relationships are enforced only on the PHP side, which is an area that could really use improvement.