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 was asked to write a report on different data storage types.
Data can be stored in
Text files.
Different possible data bases:
Oracle db
Microsoft SQL Server
DB2
MySql
PostgreSql
SqLite
excel sheet.
Microsoft access.
Proprietary database.
I was able to gather a little information on this, any help can be appreciated. Please!!
In what ways can data be stored, so that it can be queried using a programming language and data can be extracted by using a programming language.
The real answer is, any structure that persists between application sessions. This includes flat files (text, csv, xml, etc.) and RDBMS (Relational Database Management Systems).
MySql/DB2/Oracle/SQL Server, these are all RDBMS'. Excel sheet, text files, etc. these are flat files.
Each has their own place. For high performance and a lot of Online Transaction Processing (OLTP) you'll want to go with a full-blown RDBMS. For small data that isn't often written to, something like an XML file would suffice.
What you're asking is a gigantic topic that many devote a large portion of their professional careers with. It's impossible to give you an all-encompassing lesson on these.
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.
What is the best database to start learning stored procedures.
Taking into account that each database has its own syntax. Like Postgresql has functions, SyBase, Oracle, MS SQL, DB2 has some sophisticated procedures..
Is there is some db, you think is good one to use, let's say, for students to demonstrate the principles, knowing which, the students could jump to some specific database without big problems? Something that stays at the middle of the popular set of dbs.
As you know that almost all modern DBMS support stored procedures and vary in syntax. So that's pretty much the personnel choice. But the most easy to use DBMS is MySQL. That can be comparatively more helpful then Oracle, MSSQL or DB2 especially for new students.
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.
Why is a data layer used while we can write most of the code in stored procedures itself? What are the advantages and disadvantages in it?
Data layer is an important layer in 3 tier architecture, which handles all the database related tasks. My question is that, whether we can achieve this using a stored procedure itself in most of the cases? In that case, what is the major advantage in using that layer?
EDIT:
The question was just to get clear idea about the usage of data layer and database stored procedures. I have got an answer below which helped me in that.
The 3-tier approach is for when you wish to maybe use different Database Engine types.
From Multitier architecture
Data tier
This tier consists of database servers. Here information is stored and
retrieved. This tier keeps data neutral and independent from
application servers or business logic. Giving data on its own tier
also improves scalability and performance.
In stored procedure goes your query logic, in data access layer you connect with database engine
MSDN,
N-Tier-Architecture-and-Tips have good insight on n-tier architecture
You can't unit test stored procs very easily because you can't easily mock the data in the database
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.
We are new to NoSQL and now are starting on a project that aims to record sensor data from many different sensors, each recording a timestamp - value pair, into a cloud based database. The amount of sensors should scale, so the solution should be able handle the sizes of hundreds of millions or possibly even billion(s) writes a year.
Each sensor has its own table with key(timestamp) - value and sensor metadata is in its own table.
The system should support search functions such as the most recent values (fast data retrieval) of certain sensor types and values from time frame of sensors in certain areas (from metadata).
So the question is which cloud database service would be most suited to our needs?
Thanks in advance.
Couchbase is a great option for this type of use case.
Try Apache Cassandra. DataStax provide easy to install packages that includes some useful extras.
I wholeheartedly agree with #Ben that this isn't an answerable question; nevertheless, I would at least consider the reasons for choosing a simple k/v type store over a typical RBDMS. It sounds like this data will likely be aggregated and counted; an RBDMS will typically answer those questions very quickly with correct indexing. 1B writes/yr (or even 30B/yr) is really not that high.
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 9 years ago.
I'm looking for a document oriented database to store over millions of invoices with fast reporting speed.
I find some options such as MongoDB, Ravendb, Couchdb but I don't know the risk of performance failure vs. Sql Server Xml type column.
The source of this question is here.
Fast reporting is something that you want to do in sql server. I'm not aware of a good NoSQL solution for this scenario.
RavenDB has the index replication bundle that enables you to replicate an index to a sql table, so that you can do some advanced reports on them.
Reza,
RavenDB seems like a good match here. It all depends on what you are actually calling "reporting".
Doing things like "how many invoices are there for last month" is easy in RavenDB.
As is doing things like "how much money does Northwind owe us?"
We don't recommend RavenDB for reporting for the specific case where you have dynamic reporting needs such as the need to do on the fly aggregation.
What is it that you are actually trying to do with regards to reporting?
That aside, invoices is a nice place where RavenDB truly shines, especially given the other parameters of this question with the dynamic nature of the invoices.
but I don't know the risk of performance failure vs. Sql Server Xml type column.
Epic fail already here. Invoices are relational data in most cases (in all you need) so address links, line items, numbers and prices are in tables, not XML data type. This is the "ok, so - you planned to wkr at McDonalds, not in our team?" level design decision.
What line items and invoices may have is additional data in XML (like timesheets etc.) but if you run accounting, you dont run it as documents.
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.
So I am working on a mini-project for the summer to keep my coding skills sharp. I will be using the Qt4 and C++ to make a classroom management system for college professors. I just came up with the idea like 10 minutes ago so I don't have much.
One question I have is what is the best way to store student/class/assignment information so that the software could still be portable and used my different schools.
My first guess would be a MySQL database. I need a gurus opinion on this one though.
Since different sites have different database preferences you might wish to use a layer such as ActiveRecord or PDO or ODBC to abstract out the specific database that your end users want to use. This would allow people to deploy onto PostgreSQL or MySQL or whatever they prefer.
A good choice for single-process server systems could be SQLite3. It's not suitable for all systems, but if your system is designed to scale to a few dozen users at most, it'll probably work fine. (The amount of work you'd need to put into a server to make SQLite3 scale into the hundreds or thousands might argue for planning for a database server environment instead.)
http://www.sqlite.org/
might be a good option. It is embeddable so you don't need a specific database instance running wherever you deploy it
also, http://www.microsoft.com/sqlserver/2005/en/us/compact.aspx is an option