TDengine Want to Use Multiple Path for Storing Data - database

I am thinking about using different path when storing databases, and noticed the following config in TDengine's config file.
# data file's directory
# dataDir /var/lib/taos
Is it possible to set multiple dataDir and letting TDengine store files in several paths?

Actually, TDengine support multi-tier storage system, which you can store in different path(files) and set different tiers. However, it only support in the TDengine Enterprise Edition, which is a paid version.

Related

ArangoDB - Where database files are stored?

I am using ArangoDB community edition, I have upgraded the ArangoDB and ArangoDB client softwares, hence I can see multiple installations of ArangoDB on my machine.
Well, depending on my activity I would like to uninstall unused installations.
To have a back-up I would like to save the actual database files.
I would like to save these different database files. viz : Db1 , Db2 , Db3
Just in case I mess up installations or something.
There is no option to download the complete download of database. We can only export Collections as JSON as of now
I would like to know what's the typical location where the database
files are stored.
I did complete check of below locations and I dint find database storage files.
C:\Program Files\ArangoDB3 3.X.X\etc\arangodb3
C:\Users\Prateek\AppData\Local\ArangoDB3-client 3.X.X
and other locations by Search function.
Having multiple installations of ArangDB after upgrading sounds like a bug. Would be nice if you would open a github issue for that.
The recommended way of making backups of your data is by using arangodump and then arangorestore to restore the data.
The actual default location where these database files stored is
C:\ProgramData\ArangoDB\databases
ProgramData is usually hidden under Windows.
Each collection has its own folder and has 2 files;
parameter.json
journal-NNNN.db
We can also see other ArangoDB files under C:\ProgramData\ArangoDB such as
journals
rocksdb
Even though I have had multiple installation showing up due to upgrades these database files are common. I verified this by switching to different server by running arangod.exe in Administrator mode and then calling respective arangodump by switching to that location.
Note : to get the version arangodump is running for we can check from arangodump -version true If we dont run particular aranghodump(exe) this is fetched from environment path variable.

Can I load solr schema file from another server?

I am running solr on 5 different instance. Making change in schema/dataconfig file is a big task as I need to make changes on each server.
Can I load schema file from a server? So that same path can be defined in each solrconfig and changes will be reflected on each solr instance.
If you're running Solr on multiple instances, you should really consider moving to a cluster based installation (i.e. SolrCloud). This will give you a common schema across servers and allow you to easily create collections and make changes across all nodes in your network at the same time.
You can use a shared file system, but it'll still require you to access each server (which you can do through the core API if you want to automate it) to reload the core to make it pick up any changes to the schema.

Truly virtual FTP

I am looking to set up an FTP server without connecting it to a file system.
I want to use a database to store which of the many large files on my site each user will have access to. Because of the number and size of the files involved, the files cannot all be stored on a single server so a link based setup is not useful.
I am imagining an FTP server that will act as a pass-through for a backend CDN that stores all the files and checks a remote database for which files to present.
Does a system like this exist? If it doesn't exist, Which open source FTP server would be easiest to modify to suit my needs?
Have you looked at JScape?
It costs money but has the capability
Since you are on StackOverflow, I assume that you are ready for coding. In this case you can use FTP/FTPS server component, included in FTPSBlackbox of our SecureBlackbox product. It lets you handle all operations yourself, so you are not bound to the file system in any way.
We also have SFTP server (SSH File Transfer Protocol) with similar design.

Exporting database on oracle

I have a DB on oracle on Windows Server 2003. How do I export it with all the data and put it into other Windows server?
Use RMAN to take a full backup. Then restore it on the new server.
See Clone using RMAN Article
You can use Oracle Data Pump to export and import database. Quote from documentation:
Oracle Data Pump is a feature of Oracle Database 11g Release 2 that enables very fast bulk data and metadata movement between Oracle databases.
Procedure is like this:
Export existing database using expdp utility
Install Oracle database server on new Windows server
Import database on new server using impdp utility
Check this link: Oracle Data Pump. There you will find complete documentation and examples how to use this utility.
If you are wanting to create an exact copy of an existing database on a new sever of the same operating system (though not necessarily the same O/S version) and the same Oracle version, the quickest and least problematic method is to just copy the database files. This is often referred to as database cloning, and it is a common method DBAs use to setup development and test databases that are intended to be exact duplicates of production databases.
Stop all instances of the database on the existing system. You could login to each instance "as sysdba" using SQLPlus and run the "shutdown immediate" command. You could also stop the Windows Services for the instances. They are named OracleServicesid where "sid" is the instance name. Usually, there is just one instance, but there could be multiple instances to a single database. All instances must be stopped for this procedure.
Locate the database files. Look for an "oradata" folder somewhere below the Oracle root folder and then find the folder for the database sid in there. (There could be multiple oradata folders. You need to find the one that has the folder named for the SID of your database.) There are also the files in the Admin folder for the sid as well as the %ORACLE_HOME%/database folder. If DBCA had been used to create the database, then the location of all of these files varies by the Oracle version.
Once you have identified all of the files for the database, you can use any method at your disposal to copy these files to the same locations on the new server. (Note: The database files, control files, and redo logs must be placed in the same locations (i.e., file system paths) where they exist on the old server. Otherwise, configuration files must be changed and commands must be run to alter the database's internal file paths.) The parameter file (initSID.ora) and server parameter file (spfileSID.ora) must be placed in the %ORACLE_HOME%/database folder.
On the new sever, you must run the oradim utility. (Note: oradim is an Oracle utility that is specific to Windows and is used to create, maintain, and delete instance services.) Here is a sample command:
oradim -new -sid yourdbsid -startmode automatic
Startup the database with SQLPlus, and you should be in business.
This is a general overview of the process, but it should help you get the job done quickly and easily. The problem with other tools is the need to create an empty database on the target server before loading the data by whatever means. If the target server has a different version of Oracle, it will be necessary to run data dictionary scripts to upgrade or downgrade the database. (Note: A downgrade may not always be possible.) If the new server has a different O/S, then the above procedure would require additional steps that would significantly increase its complexity.
It also possible to duplicate a database using RMAN. Google the words "clone oracle database using rman" to get some good sites on how this is done using that tool. If you are not already using RMAN, the procedure I have described above would probably be the way to go.

Managing databases in Open Source Software Projects

I was wondering how databases are managed in open source projects which are usually hosted in repositories like CVS or SVN. Placing codes in the SVN is very logical as it allows different team members to get updated pieces of code but how about databases?
Are their schemas and contents (.sql files I assume) placed inside the SVN too? In this case if I were creating a web application, would this require developers to keep on updating their local databases with the newest .sql file?
Or, is it more like having a central server which members can modify and their software just connects to over the net?
I'm planning to start an open source web application project (which requires the use of a database) but am a bit confused of how to go about the database management part.
Typically you would include one or two things:
Schema creation scripts
Initial data to be loaded into the database
Both of these should be text files. If your data needs any special processing before it can be loaded into the DBMS, then include a tool for that too.
One thing you should not do is include any particular binary database file in your source control. For example, a SQLite database file would not be appropriate. Binary database files are not normally portable across architectures or versions.
In my experience these types of applications usually include a database set up included with the build. Usually you have to install the DB where you need it then install the client. Also, usually these databases are also open source like MySQL or something.
This depends on the project you are doing. For example if all the developers are in same location in one company, the central database server may be applicaple. If the developers are distributed around the world, then the central database server is probably out of the question and every developer creates his own copy of database for development.
I would think that most common option is that every developer uses his own database.
In any case you'll want to keep the schema creation and initial data creation files in version control. This way all the developers can create a new database easily.

Resources