I'm using PGAdmin 4 v6.4 on my mac. I have a master password set and a number of passwords saved for databases so I can log in without needing to type the individual passwords each time. How can I view these saved passwords? In previous versions, it seems they were simply stored in a plaintext file somewhere, but that no longer seems to be the case
Related
Is it possible to lose data during the detach/reattach process?
I'm trying to figure out where I went wrong this weekend..
I was moving user databases from one physical HD to another.
I was using the SA account, detach database, copy both .mdf and .ldf to new location, then reattach database with path pointing to new location.
During this process detach/reattach the MSSMS console faulted saying default database no longer available (or something similar).
I reconnected with a different account and resumed the moving process - I didn't know how to change the default db at the time in MSSMS.
I verified that all the databases were listed, and double checked the file size of the original and new location and they were the same. Here I should have looked at the actual data, but didn't.
Later I came to find out that some of the most recent data (last 4 months) was gone from one database - I'm assuming it was the database when the console faulted.
I have a shared accde file on a network drive. Occasionally we will have an inconsistent state problem. The error message appears below. It seems to be associated with network connection interruptions for even one user. We have an example when a user unplugged the Ethernet and switched automatically to wireless and other examples where users have left the database open overnight, perhaps when a machine hibernates.
Once this happens the one user cannot work and no one can open the accde file. Other users who have the database open can continue to work.
After the problem occurs it remains until everyone closes the database. At that time it completes whatever recovery it requires and all users can get back in.
This was disruptive when we had six users in one room. Now we have 17 in two cities and a few work-from-home users. It's becoming intolerable.
The obvious answer is to move away from Access. We're working on it but it's a long way off. In the mean time I would appreciate any advice.
Is there a way to prevent the problem entirely?
Is there a VBA way to detect the problem in the instances that are not showing the error message?
Is there something I'm not thinking of?
What would you do?
Error message:
Microsoft Access has detected that this database is in an inconsistent state, and will attempt to recover the database. During this process, a backup copy of the database will be made and all recovered objects will be placed in a new database. Access with then open the new database. The names of objects that were not successfully recovered will be logged in the "Recovery Error" table.
The solution that Microsoft gives is Splitting the database, which just means to put the data elements on a shared server, and everyone has their own copy of the front end.
This might cause problems if that front end needs to be updated (e.g. additional forms). Details here:
http://answers.microsoft.com/en-us/office/forum/office_2007-access/microsoft-office-has-detected-that-this-database/3fb41c70-f7ba-41dd-a847-e62203071466?auth=1
Check the row count in the tables, the tables most likely have large amounts of data creating latency on the read and write queries, causing the locking.
Archive older data and keep the database small and neat, perhaps create referenced databases for archived information
I gather that your MS Access database is getting corrupt when up put it on a shared drive. A Microsoft Access database may get corrupt when in a multi- user environment. Here are the workaround that you can use in order to fix it.
Step 1: Run Command Prompt as Administrator
Click on the Windows icon and type Command Prompt. Then right-click on the Command Prompt and choose Run as administrator option.
Step 2: Execute Compact and Repair Database Command
In the command prompt window, type the following command and then press ‘Enter’.
msaccess <database file name> /compact
In the command, replace <database filename> with database path. For instance,
msaccess "C:\Program Files\Reports.mdb" /compact
This will start the process to compact and repair the faulty Access database file.
Otherwise, You can check out this thread for an alternative solution : https://dba.stackexchange.com/questions/71906/ms-access-mdb-ldb-database-corrupted/171275#171275
I have an SSIS Package which is used to connect Oracle. I used the Oracle Provider for OLEDB connection manager in SSIS. I have specified my server name, user name and password, selected the check box "Allow Saving Password". It is running fine on my machine but when I give a copy to another developer, he fails to run as he gets null password error. Is there a way to save password in SSIS Package so that we don't need to worry about that?
Your goal is the Package Protection Level. By default, it is set to EncryptSensitiveWithUserKey. This means, that all passwords are encrypted using the authors Windows Account. As soon as another user tries to load the package, the passwords will be lost.
There are some other options for this package property. One option would be to use EncryptSensitiveWithPassword or EncryptAllWithPassword. Using these options, anyone can open an run the package as long as he/she has the password.
Yet another option would be to use the option DontSaveSensitive. You will then use the Expressions of the Oracle Connectionmanager to overwrite either the password or the full connection string. I can confirm that this is working pretty fine, we are using this method for our Oracle passwords for years. As this option results in having the password saved on your system(s) unencrypted, you need to be sure to secure it in some other way.
Further reading: https://msdn.microsoft.com/en-us/library/ms141747.aspx
You can utilize XML configuration files to store the passwords, but since they are stored in clear text, additional safety measures would be advised to protect the files from prying eyes.
This MSDN blog illustrates how to add and utilize configuration files very nicely.
Im building an app which uses Sqlite DB.
Users can enter their information into the db and retrieve them.
However, I want them to be able to backup the sqlite db.
What I did was putting the sqlite db in the documents folder, so they could retrieve it out using iTunes.
For example if the ipad is faulty, i want them to be able to transfer the sqlite db to another ipad.
The problem now is, I dont want them to know the information inside the db, should say the db structure.
So how can I build a db that is able to read by my application only? and when they use sqlite browser to open, they wont be able to see anything.
I'm looking for something simple. Possible to have the db to prompt a password before opening it?
Here is the link to your answer, SQLCipher is the best thing, which will encrypt the whole database and if any one get the database from the iOS device, any how , still it will prompt for a password otherwise is will not allow user to see the same. even with Command prompt the user will not be able to see the database.
Hope this will be usefull....
I have intersystem cache database file (cache.dat around 160MB). From management portal, I created a new database which point to my file.
But when i go for mounting the file into database, it gives me an error -
ERROR #86: the database default collation is not available
Please help me on this.
For your information i am using intersystem cache version 2011.1.2
Make a COPY, convert copy with cvendian:
noddy#chopin 11:24:36 /scratch3/noddy/chopin/mgr/db16k
$ ../../bin/cvendian CACHE.DAT
This database is little-endian.
This database has a block size of 16384 Bytes.
This database has 1 volume and 1 map.
The last block in the primary volume is 768.
Original manager directory is /home/isc/cache/mgr/db16k/
No extension volumes.
Done converting CACHE.DAT to big-endian
Hope this appears in a timely fashion
That means that you either trying to mount Unicode database on 8 bit system (or vice versa) or you are trying to mount a database with collation that is not installed to your cache system. In the last case you will need to install a locale file with required collation. You can look into cconsole.log file in mgr directory to see if there is a better error description there.
I had this problem, and I believe it was because I was trying to mount a database that was big-endian on a little-endian system (or maybe the other way around--doesn't really matter.) I'm not certain this was the problem, but it's the only difference I can think of between the two databases I was trying to mount.