We have ROR site with a MySQL database. There are many tables which we would like read/write access to, but we have not written this function within our current admin panel. I was curious the drawbacks of using an ODBC tool to perform all reading/writing of values to the database from the admin panel. Also, does anyone have any suggestions for ODBC tools that we should look into for an easy to use software.
I think that you haven't actually started using Rails, else you wouldn't ask this question. Go spend some time reading the documentation and a few getting started tutorials.
http://guides.rubyonrails.org/
Rails comes out of the box with ActiveRecord, an ORM layer. Once you get familiar with it, reading/writing to the database will be a breeze, independent of what database you are using.
Related
I'm creating a mobile app for an existing website and trying to connect to a local instance I have running on a MySQL workbench. I've seen others recommend against the use of MySQL but I'm stuck with it, since that's the current database. I'm using expo to run my React Native code. Do I need to use a server, like "MAMP?"
Let me know if there is any more info that is needed.
You cannot connect your app directly to your database.
You will need a server/API that acts as an intermediate between the app and the DB. You can code it in most programming languages and if you know PHP, having MAMP on your system will allow you to build your API with PHP.
I've seen others recommend against the use of mySQL
You should definitely question their reasoning. I've been using MySQL for many years now in small and big projects and it has never been an issue. If they're comparing it to non-relational DBs like Mongo, I can understand, it's easier to setup and maintain a NoSQL database than a relational one.
I assume you're not that experienced but I still purposefully used some terms that may be new to a beginner. Since I don't know your skills, I will refrain from pointing you to specific tutorials/articles.
I recommend you to Google anything you don't understand from this answer.
I am trying to understand the trade-offs between going with MySQL or PostgreSQL on AWS.
Some considerations for me are that I am an amateur database user, so I need to be sure resources are available which allow me to overcome problems quickly. Along these lines, I bought the book 'PostgreSQL on the Cloud' and was all set to go with PostgreSQL since the book laid out a great use case.
One thing held me back though is that it is important for my work to be able to to easily use Excel as a front end for importing and exporting data into and out of the Database on AWS.
It looks like MySQL has an open extension which is fully integrated with Excel and is also well documented. My research into PostgreSQL uncovered a much more uneven integration with Excel and a lot of long painful group frustration a closer integration has not already occurred.
Right now, I am leaning to MySQL, but want to make sure I am not missing something.
Thanks!
Microsoft touts a PostgreSQL plugin as well: https://support.office.com/en-us/article/connect-to-a-postgresql-database-power-query-bf941e52-066f-4911-a41f-2493c39e69e4. Never used it, so can't comment on it.
You mention you are a beginner, so I'll add... be careful about security with either of these options. There are options to encrypt the channel between the client and server, which you indicate is running on AWS. If not secure, anyone would be able to effectively monitor the connections, extract credentials, and do whatever to your AWS-hosted DB. Generally, cloud-hosted DBs should be behind an authentication/authorization login process.
I am recreating an old database that's in MS Access with company data, contacts, conventions etc. but I have never done something like this. In the past few days I learnt to use MS Access and started recreating the tables to fit third form, creating table relationships etc.
But I got stuck when I started searching for a program/programs that could help me create an easy to use visual input form like in MS Access sparing me from having to delve into SQL and HTML.
I am not a native english-speaker so I couldn't really word what I wanted sufficient enough to find related google hits, I have found applications like Aptana Studio, Heidi SQL, Dreamweaver and so on. My question is, is there a program where I can manage the tables inside the database, create forms to input data with, all (if possible) wih a drag-and-drop designer?
I would be grateful for any number guides you guys have links for, because I just couldn't find what I wanted (possibly because of my still lacking programming expertise). Any guides touching on the topic of how to create input sites with HTML/CSS for an SQL database would also helpful if it's not possible to do without using these languages.
Thank you in advance.
Visual Studio, with SQL Server, has all of the features that you are asking for. There are free versions of both, but with limitations.
You can also use a Java and MySQL solution. To manage the database, use MySQL Workbench. For an IDE that has a drag-and-drop designer, use either NetBeans or Eclipse. For more information on either, google "Netbeans form designer" or "Eclipse form designer."
For creating and managing databases you can use the "Sql Server management studio" itself.
If you have MS office, you can use "InfoPath" to create forms and connect them to the Sql Server database. Check this link out which shows how to do it :
https://www.mssqltips.com/sqlservertip/4246/data-entry-for-sql-server--building-quick-efficient-data-input-forms-using-infopath/
I have an ACCESS database(.accdb) with tables, forms, queries, reports , modules and microsoft access class objects(VBA code). Now the requirement is to shift from access to optional database. The options that I could find by browsing are using either MySQL or SQL Server. As of now, I would like to use Access as front end to any back end database. I would like to know more detailed information regarding migration from Access to optional database. Can anyone please help me or point me to good resources.
I've used SQL Server as a backend for an Access front-end app in the past with pretty decent success. You can use the SQL Server Migration Assistant wizard to migrate the data from an Access Database to a SQL Server database.
Performing a quick search for "using SQL Server database as back-end for MS Access" will yield a number of resources on things to consider and do. You can also refer to this SO Question Can a Microsoft Access Forms application be switched to work with a SQL back end? for additional insight.
My experience has been pretty positive with this sort of migration, but it really depends upon how you've designed and constructed the application. It could be a very simple migration (a few hours to tweak and test things) to a much larger effort on your part to make sure everything works as expected.
You can use SQL Server (Express) as backend using export data from Access Menu. If you will use MySQL some features like auto_increment fields don't work fine and it will need to write VBA code to work as expected.
I'm writing the entire database system for a factory, this includes inventory, payroll, incoming and outgoing shipments, job-data, customers, etc. The database will be stored offsite on a server running Windows 2008 R2 with SQL 2005. The guy who runs the server sent me this too:
"We also have quickbooks installed on the server and we have Exchange 2010 running. The terminal server is also ws 2008 R2.
There is plenty of horsepower on the primary exchange/file server. Let me know if you have any other questions.".
I know my boss uses Quickbooks to look at reports and stuff like that. I'm not sure how relevant exchange 2010 is, nor what the significance of "terminal server is also ws 2008 r2" is. My boss wants me to write the entire system in ms access 2010, but I feel like this will be a lot more work than simply writing it in MySQL. Will my boss still be able to look at his reports in quickbooks if we change the database to MySQL? What would be a good database technology to use? I feel the most comfortable writing it in a scripting language using MySQL, but would still be happy if I could write it in something like C/C++. I've been trying to learn access, and it seems that setting up a front-end and back-end database in access would be a pain in the ass. There are going to be several sectors in the factory that will be using the client-side software to run queries and insertions into the database(I think around 5-6).
If I can write this thing in MySQL, I think I could do the whole thing fairly pain free, but I fear that I can't because it will be incompatible with Quickbooks and the previous database(Although I hear converting is fairly easy). Mostly just Quickbook compatibility is my problem.
How horrible would it be to write this thing in Ruby?
Thank you, any help is greatly appreciated.
I don't mean to be a spoil sport but there is a tremendous amount of naivety expressed in this question. It's hard to imagine that you will be successful in designing and implementing such a large system without a basic knowledge of the technologies involved.
A few thoughts:
Quickbooks already covers most of the features you say you will be responsible for implementing. Are you supplementing the existing Quickbooks system, replacing it, or what?
Quickbooks uses its own (extraordinarily slow) database engine. It isn't "compatible" with SQL Server, MySQL, or Access.
SQL Server 2005 is a database. You don't use a database with it, you use it as your database. A Microsoft-centric organization such as the one you describe is not likely to be interested in installing yet another database server like MySQL.
MS Access encompasses both a database "engine" (called JET) and a desktop development environment. The engine can be used with other development environments and the development environment can attach to other database engines (most often SQL Server, but others work too). When you say the boss wants to write the system in MS Access you need to be clear whether he means the engine, the development environment or both. (My guess is they want to use Access as the front-end development platform and SQL Server as the data store).
You will not write a system of this complexity in a month. You probably won't even design it in that time.
Quickbooks can use MySQL as a datasource (or just about anything else), but you'll need to make your database conform to the Quickbooks way of doing things: i.e., your tables will need to match the QB table structures. It sounds like you just need a front end (data entry forms and reports) and a custom back-end. Access can quickly turn into a nightmare if you don't put in some up-front design thought, but it does give you forms & reports & web pages free in a neat little package. Make sure you use an Access Data Project (adp) that's connected to a SQL Server back end. Access does have its own native database, but everything gets stored in one local file and it's not good for applications that will be accessed by multiple people in multiple locations. It also gets complicated when you need to make a change and roll it out to all of your users.
Another option is to look into a customizable web platform, like SalesForce or MS Dynamics. That will also let you create your own tables, forms, and reports, and updates are immediate for all users, but you'll have ongoing monthly user fees. They look great on a resume, though!