We are using PG views for the graph. Currently is looking for the easiest way to backup or transfer data.
How can we backup existing graph or anyways to transfer/duplicate to another server?
Any solution would be appreciated. Thank you.
Since PG views are composed of regular database tables, you can apply all existing methods for export/import, such as Oracle Data Pump (expdp/impdp). Please note you need to include or re-create the metadata tables.
If you export/import the schema, the metadata tables should be included with the data source tables.
If you export/import selected tables, you can include the meta tables or re-create them after the import. Re-creating option is more robust when the metadata table definition is updated between the product versions.
Metadata Tables for PG Views:
https://docs.oracle.com/en/database/oracle/property-graph/22.1/spgdg/property-graph-views-oracle-database-tables.html
Related
This is a conceptual question, I am a developer who is familiar with Mongo & Postgres. In both of these DMS, you never have to create a table before using it. I don't really know how it works under the table but I create my Schema's in Mongo or my classes in Postgres (I use SQLAlchemy ORM) defining the structure of my different tables.
With DynamoDB I understand I can do the same but before adding an item/column into the table I need to check if the table is created? I don't really get how that works. Do I just create the tables the first time I create my db instance and if I add more tables I just create them once??
I understand the reasoning behind DynamoDB needing me to create the tables explicitly because they will allocate a certain amount of space in anticipation of the items that will be stored there but I have looked around and not really found a best practice or advice on when I should be creating new tables in DynamoDB?
Think of it this way: the DynamoDB table is the same as your Postgres database, not your Postgres tables. It's a piece of infrastructure that your service depends on, so you need to create the table at the same time you would create your Postgres database.
Also be sure to understand that unless you're doing some very, very complex thing, dynamoDb is intended to be used with 1 table per service. So if you're thinking "I need 4 tables", I'd suggest looking at this great aws video.
Does Firebase offer a way to view and update our data in a more human-readable format, rather than large trees of text?
Parse has a great browser for viewing and updating tables of data, which I found invaluable. It was easy to find specific data, and columns had helper menus for creating pointers and references to objects in other objects/tables. It was also easy to translate spreadsheet data into databases of users/places/etc. I guess I'm looking for something similar in Firebase, if it exists.
Any help would be appreciated.
Firebase is a schemaless database. Since it stores the data as JSON, it offers a visualization of the data as an editable tree in your Firebase Console. It does not offer a table view, although you could easily create that yourself.
I have a separate copy of a sql server2008 database that we used to isolate data. I would now like to bring a few records into the production database from this separate database. I am not sure of the best way to do this, but I need to transfer several tables and ensure the relations remain. The easiest way I think of is to (if possible) create another dbml data context of the separate database and set all variables equal to a new object in the new database. I realized that I am getting many conflict errors. Is there a way to have two databases coexist like this in one application? There a few minor differences in the databases. The production database does have a few added rows.
Thank you for the help,
Chris
I'm no authority so perhaps someone can give you a better solution but it seems you can't have two models in the same project with an identical table name. What you could do is create a new project in your solution just to contain the model for the separate database.
This will let you have two models that both contain a "person" object for example because their namespaces will be different. Might help to put using statements at the top of your pages that use both models similar to the below:
using PersonLive = MyProject.Person;
using PersonIsolation = AlternateProject.Person;
I created a database mdf file a while back and created a diagram of foreign keys. Lately, I needed to add several tables and there was an error saying I couldn't do the diagram because I'm not the owner.
So, I didn't update the diagram but added the tables anyway. My app seems to be working fine with the new tables. I'm using linq-to-sql and the design surface of the ORM doesn't show the connection between the new and the old tables.
My question is this: if the app works both with and without the diagram, what's the benefit of creating one? I know I can read an 800-page book and get the answer but I was wondering what the 2-3 line answer would be.
Thanks.
Diagram is just modeling tool.. no need to use it, but cool to visualise db, easier to write queries if you're not creator of db.
You can switch owner of db in options at "File" tab.
I'm having hard time to find the right solution to manage multiple modificable lookup tables (more than 40), most of them with the same structure. I'm using the repository approach but I can't make it work. Has someone a working example?
Take a look at my repository pattern for EF4.1/4.2 it allows you to easially connect to an EF4.1 DB and query it throughout your solution.
http://blog.staticvoid.co.nz/2011/10/staticvoid-repository-pattern-nuget.html
a working source application is also available here:
http://dl.dropbox.com/u/37129059/StaticVoid.Repository.Demo.zip
A tool that worked great for me is a t4 code generation template that generates enums out of lookup tables. It can save you a lot of work and keep your source code up to date when you add some new items to the look up tables.
I also use a DB with ~30 lookup tables and it was easy to set up, modify and use (even though I did not knew much about t4 templates before).
http://erraticdev.blogspot.com/2011/01/generate-enum-of-database-lookup-table.html