Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
COURSE of the MONTH
9 days, 22 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Informix - dbexport/dbimport.. silly question
Posted on 2012-12-28
Say you have DB1.. if you successfull run dbexport on that database. And let's say you lose the exported file(s).. is the data still contained within DB1 and in a current state that you could fire up the instance and access the data like nothing happened?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
5 Comments
You should be able to. About 99.9% of the databases don't actually delete the data during the export process, they just make a copy of it in some sort text readable file.
Active today
dbexport is nondestructive. It basically generates a bunch of SELECT statements, so you'll want to disable SELECT triggers before you run an export.
- Gary Patterson
- Gary Patterson
Thanks so much Gray. Last thing.. once you dbimport into the new db on the new server.. does this new db need to already be as big as the old one or will it dynamically increase?
Active today
When you run dbimport, you specify the name of an existing dbspace (the default rootdbs dbspace is used if you don't specify a dbspace).
A dbspace is just a logical collection of chunks of disk space used to hold the database.
The dbspace you specify needs to exist, and be large enough to hold the new database being imported.
All of this is covered in much better detail than you'll get here in the Informix documentation. You'll find information on creating dbspaces, adding chunks to an existing dbspace, importing/exporting, and more:
http://publib.boulder.ibm.com/infocenter/ifxhelp/v0/index.jsp
- Gary Patterson
A dbspace is just a logical collection of chunks of disk space used to hold the database.
The dbspace you specify needs to exist, and be large enough to hold the new database being imported.
All of this is covered in much better detail than you'll get here in the Informix documentation. You'll find information on creating dbspaces, adding chunks to an existing dbspace, importing/exporting, and more:
http://publib.boulder.ibm.com/infocenter/ifxhelp/v0/index.jsp
- Gary Patterson
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Microsoft Access is a place to store data within tables and represent this stored data using multiple database objects such as in form of macros, forms, reports, etc. After a MS Access database is created there is need to improve the performance and…
This post looks at MongoDB and MySQL, and covers high-level MongoDB strengths, weaknesses, features, and uses from the perspective of an SQL user.
- Query Syntax
- SQL
- Databases
- MySQL Server
- MongoDB
- NoSQL Databases, Percona
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have.
In this…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment.
To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Suggested Courses
Course of the Month9 days, 22 hours left to enroll
762 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.