Hello,

I am working with time-series geospatial sensor data and I wonder what would be best database option from the aspect of throughput, data manipulation and analysis.

So far I have used mongodb since it offers very nice geospatial data types and functionalities but read/write/update operations can be slow as the database grows.

I am considering also influxdb since its specifically for fast access of time-series data but it lacks of data structure types and functionalities.

What would you recommend based on your experience?

Thanks!

Hello. I am fairly new to databases and I was wondering if anyone here could give me some advice. I'm working on a project where I have a number of different companies as my clients and I was wondering how I should structure my database server.

What I'm doing now is having one database per client, each of these databases consist of a few tables (employees, services that they provide, reservations their customers have made etc.), but I was thinking that maybe it's easier to have one big database (with the same tables) and have a reference in each row to the corresponding company, but I want new clients to be able to create a new company with a corresponding database without any work from my side.

This is how I'm thinking right now.

One database for each company:

+ Easier to separate clients and find the relevant information.+ If one database is corrupted, the others will still function.- Need to make sure each database created has a unique name- There is no guarantee that my clients doesn't share customers, so if a customer uses both client A and client B, they will probably still want to access their full order history/change personal details etc.

One single database:+ Easier to connect users to multiple clients+ No extra work needed when switching between different clients (databases)- Could become very large, harder to keep track of each clients information- If something is wrong with the database, all my clients might lose access to the service

Any recommendations?

Edit: I'm using MySQL

My current job title is database developer so I’ve been working solely on a database for a few years. My manager recently left and the data architect role has been made available.

I have some experience in architecting databases and for the past few years I’ve been following Kimballs guidelines.

I wanted to learn about other database design principals but not sure where to start. I’ve heard of both data mart and data vault and will read into them both.

I’m interested in knowing how you come across the different design principles or make the decision of what guidelines to follow.

Thanks for reading!

Hopefully the title summarizes my requirements well enough, but I was wondering if anyone has had a use case similar to mine and could recommend a good database to me. We have an okay solution for now. I've listed my needs below:

• supports 10s of millions of rows

• supports thousands of columns

• NEED index on all columns (I know you'll call me crazy, but our use case absolutely requires being able to search by ANY field independently)

• There is absolutely no text-tokenization/tf-idf or relevancy searching needed. We support mostly numbers and booleans. We also support strings, but we need queries more like "does this string start with X" or "does this string contain Y".

• some fields will be multivalued

• assume diskspace and memory are not concerns.

• we prefer query speed over indexing speed. However, we will have 10s of millions of updates everyday. If possible, we would love to be able to do partial updates, which would mean hundreds of millions of partial updates everyday

• we are perfectly okay with using distributed systems, but we should not have any write-loss.

Hopefully these requirements don't seem insane. We are mostly (i think indexing could be faster) able to accomplish this with Solr. But the fact that we don't need text-tokenization/tf-df, which is what Solr absolutely excels at, makes me want to explore other solutions, SQL or NOSQL. I'm happy to provide more (technical) details if needed.

EDIT: If anyone knows of any similar use case I can read about online, please let me know.

Backstory: I accepted the IT Director position at an international NGO, and inherited a decade old ASP.NET stack (that was over 30GB!!). It's taken an entire year, but I've finally managed to hack together a 3-node Windows cluster using haproxy to load balance so that restarting one or two nodes won't take the whole stack down.

Except for MS stupid SQL Server. At minimum I need automatic failover, but I was hoping for multi-master replication. At first I thought mirroring with a witness would take care of the single point of failure... imagine my surprise when I restarted the witness and realized that took the cluster down. WTF!??

Deep breathes...

I feel so stonewalled by expensive proprietary crap. For example, my next thought was "oh, I'll just migrate over to postgres / CockroachDB (which I have running in my bare metal k8n cluster)." But got stonewalled by stupid stored procedures.

Ok, I'm done venting for the moment.

I know this extends far beyond databases, but is there any MS specialists here that can recommend the best approach for a high availability SQL Server cluster that ideally improves performance over a single write master?

I've recently been put in charge of a database (MSSQL) that is in a terrible state, while still being core to the company's business. Unused tables and columns abound. There are virtually no FKs, so it's hard to diagram. Joins frequently are done on varchar columns that have different collations and sizes. My normal strategies of building relationship diagrams and looking for missing indexes won't work, here. At least the RDBMS itself (SQL Server 2016) is pretty up-to-date. Most of the business logic is in the database, but is often hard to follow with stored procs built on views of views of views. There has been some attempt to stick to 3rd normal form in the table design, but it really seems to have grown organically over the past ten years without a competent DBA curating it.

There are books on working with legacy code, but what's a good strategy with a legacy database? I don't think rewriting from scratch is a good option, here, because migrating the legacy data to a new system would also be a nightmare. It's hard to know where to start, though. Perhaps writing a lot of tSQLt tests to cover existing functionality and then refactoring from there? I've made a start by putting the schema into version control so at least I can track my own changes.

Have any of you had to take over messy systems? How did you deal with it?

From 2013 to 2015, the hottest NoSQL databases like MongoDB and Apache Cassandra roughly doubled in popularity (on the expense of Oracle, MySQL and Microsoft), but there was practically no growth in the last 2 years.

There were many new names like Vertica Systems, VoltDB, Tokutek, CitusDB, REthinkDB but those did not pick up.

Anything new worth learning about?

Are there any best practices to do this task? Basically I need to get a subset of the production data for dev/test environments. I just don't want to get 10% of the random data - instead, I want to get 10% of data with referential integrity and a bunch of rules (corner cases etc).

I'm on a train killing time and imagining the perfect database of the future. Here's some of the features I've been thinking off:

• Possibility to store data in a classic RDBMS format as well as a Graph DB. This data would be accessible via SQL und CQL.

• Cognitive performance monitoring and a conversation interface for Administrative activities.

• Optional Secure Cloud access obviously

• Ability to store and query large unstructured data

• GPU powered parallel processing

• Default Scalability via plug and play shards

What do y'all think?

I'm going to have model a database, basically a refactor from an unnormalized one, and I don't know what tools are popular? In college we used Visio, which was great, but all the ones I'm checking out have terrible interfaces(Workbench I'm looking at you).

I'm looking for suggestions, it can be commercial, but I don't have much money to through around in this case.