As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm a java developer, currently starting developing a hospital management system that will server patients, doctors, accountant, .... etc the system is really huge that may have 900,000 records/day, data is really growing so fast, for that i'm confusing in which database to use since i have the following options: (Percona Server(Mysql), Oracle, SQLServer), since the application will run on network with average of 45 online users.
I hope to find a good answers here.
Thanks in advance
If you have been working with MySQL for 6 years then stick with it!
You don't want to add the burden of learning another database as well as having to develop your application.
If you are unsure if MySQL is up to the job then run some tests. Write an app that runs multiple threads inserting 1M rows and see if your servers can handle it.
I'm guessing the brand of the database you choose will be less important than the performance of the platform (machines) it is running on.
There is no good or bad answer to this question. Basically it is as good as the DBA knowns to manage it.
If asking this question it would be wise to group a team of people well known with various systems to find out the best practice. To answer such a case, even more with very sensitive data, it is not just a simple solution which will do the trick. A thorough process of decision making is very important. Not only from a technical but also from a security and business side.
As per as think your database is large you can go with oracle.but the decision also depends on the expertise of people working with you and availability of resources.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm new with Google Web Toolkit and i have some questions about the tool.
First of all, what i have to know to correctly program for GWT? It's ok if i use the GWT Designer to make the GUI?
Second, how i persists all the data i want to store? Use JPA/Hibernate + SQL Database? Or it's better to use AppEngine?
I'm with a great doubt how i get the data from Database to populate fields and tables on client-side.
and Last, i know a bit of Swing, so, GWT is the same? (Except Client - Server concept) ?
That's my questions. Well, thanks in advance.
First of all, what i have to know to correctly program for GWT? It's ok if i use the GWT Designer to make the GUI?
Ok.
Second, how i persists all the data i want to store? Use JPA/Hibernate + SQL Database? Or it's better to use AppEngine?
It's your choice. AppEngine has it's limitations. For example, it scales but may not be the best choice for multi-player games if you need data updated very often and quickly. It really depends on your need/design.
If you do go with AppEngine, my experience with JPA was a headache. Objectify is much easier and the way I would go.
Last, i know a bit of Swing, so, GWT is the same? (Except Client - Server concept) ?
I guess they share the concept of using listeners/handlers for events. They are not the same though.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have experience over Relational DB's but very little over NoSQL data stores and for these two I need a well defined reason to say that one needs to move to NoSQL.
Since I cannot replicate a situation where I can push a DB to its limits and make it lose performance, let alone scaling it. Therefore wondered about to see what others had to say. May be I have been treading the wrong path path, but I have read people saying why we should move to NoSQL or how or even at what sort of different scenarios eventually leads to NoSQL. Article after article explains what Big Data is and how it is managed in the NoSQL domain and how useful it is with it architecture of being scalable, robust, ACID, BASE, Data modelling from Sql to NoSQL, etc features.
But none would provide some solid numbers. E.g. A web service that had a DB of X-TB's and eventually the queries (read/write/etc) took T-seconds or so to complete so we moved on to NoSQL to get back the performance. My concern is at what point it really did a team shift to NoSQL when they said, OK we're done with scaling and everything, lets move on to NoSQL!
So I have had to ask SO users. Maybe someone can share some valuable information. This seems to be an open issue for me as I have been trying to get hold of even just one document that explains a real case scenario where the SQL DB eventually had to be replaced with a NoSQL DB/DS/storage.
Any guidance is much appreciated.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
In this day and age, with a new NoSQL databases popping up every weekend..
Are there any good and up-to-date resources on how to pick a database(s) that will suit your web application needs?
If you're interested in trade-offs and feature comparisons Wikipedia tends to be updated more than others.
Relational Database Comparison: http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems
NoSQL Feature Comparison: http://en.wikipedia.org/wiki/Comparison_of_structured_storage_software
If you want a more direct answer you can always post the requirements you have and you'll get a lot of helpful answers. It's a pretty broad subject and, other than feature comparison matrices like the ones above, you'll mainly get subjective answers unless you have an objective question (ie specific requirements).
Cassandra vs MongoDB vs CouchDB vs Redis vs Riak vs HBase vs Membase vs Neo4j comparison
NoRAM DB => “If It Does Not Fit in RAM, I Will Quietly Die For You”
Although I would also advise considering a SQL data back end ( e.g. PostgreSQL, Drizzle ) with a cache layer, e.g. Redis on top of it. Unless you have an actual reason to use NoSQL. The reason can by the way be NoSQL is cool and I'd like to learn it, but if that is all, usually it may hurt at the end.
Does the problem have to do with money transactions? Are you going to have a distributed system?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I´m interested in both web resources and books. It´s a jungle out there, please give me a hand.
My goal is to learn the SQL language so I can query Sql Server databases within a couple of weeks.
I´ve got a programming background, and I know some basic stuff about relational databases, but almost nothing on how to use the SQL language.
Thanks to you ALL for all good tips! I will save this page as a starting point in my mission to learn SQL. Sadly enough it´s not possible to set more than one answer as "accepted"...
I don't normally go for the ' ... in 21 days' books but this online one seems reasonable: Teach Yourself SQL in 21 Days, Second Edition.
See Where can I find training/tutorials for SQL and T-SQL?
one of my favorite websites to get started with SQL is : SQLCourse
Good luck for your starting
This (w3schools) is always a nice place to start.
Try SQL Exercises
Perhaps You need to begin your own project, It is always recommended when learning something new that you fight with real problems.
http://www.databasejournal.com/ is one of good recurses,
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
here's the job description:
Experience with data mapping/extracts tools such as Monarch and VorteXML.
Familiarity with XML documents and schemas.
Minimum 1-3 years of data analysis in SQL Server environment.
Working knowledge of TSQL and SQL Server 2000 tools such as Enterprise Manager, SQL Query Analyzer, Profiler, DTS and BCP.
Working knowledge of SQL Server Reporting Services design and administration.
BSCS or other technical degree.
Healthcare background strongly preferred.
Strong organizational and communication skills.
Strong analytical thinking, troubleshooting and ability to manage multiple, concurrent projects.
Ability to meet deadlines while working in a fast-paced environment.
what is an XML schema? ive extracted data programmatically from XML files, but i dont understand what they mean by schema?
data analysis in SQL server environment - does this just mean knowing how to do joins and select statements?
SSRS (design and administration) - can someone please get me started on some basic tutorials where i can learn this?
what is Monarch and VorteXML and where can i learn the applications?
If you don't know those technologies and what they're talking about, you probably shouldn't be applying. The same goes for any job, whether or not it's in the IT field.
Are you just planning to answer the questions and then spend about two weeks stressing your nut off once you get the job. W3Schools will give you a start with schema (.xsd files). Sql server documentation will help you with the rest (patterns and practices on microsoft site is a good read).
You've got to understand that the interviewer probably has some ideas about the answers they want to hear too.
Good luck :)