DBeaver is taking around 90 to 100 times more that PgAdmin to load same amount of data to Aroura.
Tried loading with PG Admin and it loaded in minutes
Related
we have a db2 11.1.4.4 database on centos 7, file system format is xfs and the size of database is 50 TB. Sometimes it takes too long time (1-2 hours) to activate the database, instance memory usage at the time when the activate command is running is less than 10 percents of its configured value, disk I/O is ok and there is no message in db2diag.log and server log, what causes this problem?
edited:
Our database is HADR and sometimes when we have stopped the database and we want to activate it, we encounter this problem on both of primary and standby.
Thanks
Too many primary log files could slow down your DB activation as well.
I am using vs 2017 enterprise for development and an internal Azure run time environment to run the ssis packages. I am reading a ~1.5 million row oracle table and writing into an MS Sql DAN database. Can anyone explain the performance characteristics I describe below? It appears that the OLEDB Oracle driver is very efficient but then it runs terribly with the OLEDB SSIS task. Here are the run time characteristics:
ADO.net Task with Oracle Ado.net driver: ms sql table takes ~32 minutes to load
ADO.net Task with an Oracle OLEDB driver: ms sql table takes ~5 minutes to load (the winner)
OLEDB Task with an Oracle OLEDB driver: ms sql table take ~20 minutes to load
Ok, I think I figured this out. I had been just taking the MS Sql write side for granted but, in my environment, there are two drivers you can specify in an OLEDB Destination Task for MS Sql, SQLOLEDB.1 and SQLNCLI11.1 . The job that writes in 5 minutes is using SQLOLEDB.1 to write to MS Sql. The 3rd job that takes ~20 minutes is using SQLNCLI11.1 . Ironically SQLOLEDB.1 is older and many organizations are deprecating it even though it is much faster. I will be able to prove my suspicions soon and will report the final result.
We have MS Access database hosted on desktop which is pulling the data using linked Oracle tables with database hosted on AWS cloud into different region.
MS Access dB with linked tables are getting hanged with following behaviors
If we keep any linked table open - It is getting hanged (Not responding) intermittently every 1-2 minutes even though we are not performing any operation on table.
Click on any cell within open linked table
Navigating from one row to other row in linked table using scroll bar.
MS Access DB Size is around 45 MB.
Network Latency is 200+ ms from Client Desktop to Source database.
Oracle db Version: 12c
MS Access DB Version: Office 365 64 bit MSO (16.0.12730.20394).
MS Access DB is connecting with Oracle database using ODBC driver.
Any insight/guidance is most welcome since we are struggling to resolve the issue since last one month.
I have two unix servers like (server1, server2), Currently I am loading the files (record count for 1 file - 124536) to database in server1 by using sql loader. It is loading within two minutes. But I have migrated my code to server2 in this server for loading same file it is taking almost 40 minutes.
Could anybody please help me on this?
I have several heroku sites with postgres database.
The site is based on node.js - nothing else at the server side.
As I look in my PgAdmin open sessions I see 4 connections called puma: cluster worker #: 17 [app] (# is number)
They are idle but are open for many hours and the number of connections is growing. taking up more and more of my available 20 connections in the hobby-dev plan.
The last sql they run is:
SELECT "oid", "typname" FROM "pg_type" WHERE (("typtype" = 'b') AND ("typname" IN ('hstore')))
Here's a screen shot:
What are they and why do I need them?
EDIT:
As time goes by it's getting worst: