I am trying to restore database from PostgreSQL Version 11 into PostgreSQL Version 10.
I am using Windows 7 (32-bit) so I can't use the latest PostgreSQL Version. So I am using PostgreSQL Version 10.
But I am taking backup from database of PostgreSQL Version 11.
Because of which I am getting error:
pg_restore: [archiver] unsupported version (1.14) in file header
So, is there any way I can restore my database in PostgreSQL Version 10.
It would be really helpful if any can show me a way out.
Use pg_restore from the newer version to create a plain SQL dump file. Then restore to the older version from that dump file. Depending on what features you are using, the dump file may need to be manually edited before it will restore successfully.
Related
Faced the problem of using sqlcmd in sqlserver, but I do not know for which server versions it fits, I could not find it. this console does not depend on the version of sql server?
So, if I want to install sqlcmd on sqlserver 2003, it will work or need a version of the server> 2008 ???
Good day,
sqlcmd is not part of SQL Server but external utilities.If you want to use it then you need to install it (together with other tools like SSMS or separately). You can download the last version (at this time) from Microsoft directly from this link.
You should use the latest version even if you use older version of SQL Server (from 2008 and above) since the new version include support for new features. Do not use old version of sqlcmd to connect newer version of SQL Server even so it should work for basic tasks
--- update: adding some more information ---
Here you can find more information regarding how to use the tool:
https://learn.microsoft.com/en-us/sql/tools/sqlcmd-utility
Why does Redgate compare for Oracle show NONEDITIONABLE for objects?
We have installed Oracle 12C locally on a windows machine to dry run database scripts before running them on the main Oracle 12C database on a Unix machine.
After running the scripts on the local version we run Redgate Schema compare and find that some of the Views and Triggers don't match. Upon further review the only difference between the two is the word "NONEDITIONABLE". This is not part of the our script and we are unsure how this was added to the local version of the object.
CREATE OR REPLACE FORCE NONEDITIONABLE
When researching EDITIONING we thought that maybe it was because the local Oracle install wasn't a portable database (PDB), so we changed our install, and confirmed that the EDITIONS_ENABLE was 'Y' for the user.
We are restoring a dump of the main to our local, and it appears to only be the objects that existed previously. Any new objects do not experience this issue.
I was never able to find a good solution in the local 12C version install. I finally used the restored 12C version to create by own backup, which I downgraded to the 11.2 version for Oracle Express. Once I restored the downgraded version the comparison and ran the scripts I no longer experienced an issue with the compare.
I've reformatted my machine around 3 times. I'm on windows 10 and I've selected the erase all apps and files option and I'm still not able to install sql server express 2016. I'm presented with this error when trying to install.
‘Microsoft.VC80.MFC,version=”8.0.50727.4053″,publicKeyToken=”1fc8b3b9a1e18e3b”,processorArchitecture=”x86″,type=”win32″‘. Please refer to Help and Support for more information. HRESULT: 0x800736CC.
I've tried many many things. I've reformatted, I've tried running the file as admin, tried other versions such as stand edition 2012, tried to install the files while deleting 2010 c++ distribution. I've ran .net repair tool and nothing as well.
The problem stemmed when I manually uninstalled .net 4.5.1 framework using add/remove programs. I think my system files or registry is corrupted.
I think the error says, you have a 32 bit machine(processorArchitecture=”x86″) and you are trying to install 64 bit app ,which is not possible
further there is no 32 bit version of SQLSERVER from SQL2016 onwards
Some of you may have noticed that Microsoft recently released SQL Server 2016 CTP 2.4. There is one major change that I am very happy about – x86, or the 32-bit version, is no longer included. SQL Server 2016 is now 64-bit only
you can try downloading SQL2014 express version which comes in both versions..here is a link to download :Download SQL Server Express
I am trying to do dacpac deployment using SQLPackage on Linux.
My environment:
Server : Ubuntu Linux version 16.04
SQL Server 2017 latest release candidate version RC1.
SQL Server installation is successful and I am able to create tables on SQL Server database on Ubuntu. Now I am trying to implement dacpac deployment on Linux. As per this documentation
https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-export-import-with-sqlpackage
SQLPackage executable has to be at /opt/mssql/bin. But it is not. Any idea how to install SQLPackage on linux?
When I check the older version which is CTP 2.1 I have that SqlPackage executable. Is that missed in RC 1?
-Regarding temporary removal of sqlpackage from SQL Server 2017 package-
The goal is to offer customers the best CLI experience on Linux, macOS and Windows with a multi-os version of sqlpackage that uses DACFx APIs based on .NET Core.
As a stop-gap towards this goal, we offered an early preview version of the Windows-based sqlpackage in SQL2017 CTPs on Linux to seek customer feedback. We have removed this preview version of sqlpackage from SQL2017 RC1.
Work on the multi-os version of sqlpackage is in progress but I cannot share a release date at this time. Until then, you can use one or more of the alternatives below to import a dataset on each new run of your image:
1) restore an existing .bak file into the new image using the sqlcmd CLI tool.https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools
2) run sqlpackage on a Windows machine to work with SQL 2017 running in the new image.
3) generate a script with CREATE + INSERT statements for your database or specific tables. You can use SSMS’s Generate Script wizard on Windows or the new Python-based mssql-scripter CLI (public preview) to generate the script and check it into source control if you wish. Then, you can use the sqlcmd CLI tool to execute the script in your new image. For mssql-scripter installation instruction, please see README.md inhttps://github.com/Microsoft/sql-xplat-cli
Please send me an email at sanagama#microsoft.com if you have more questions or feedback and we'll be happy to help.
As mentioned by #Lin Leng-MSFT, sqlpackage has been removed from the installation package as of RC1. That said "SqlPackage can still be run against Linux remotely from Windows."
I am using postgres 9.5. Suppose my system postgres got downgraded into 9.2. Will my old database works with newly installed postgres as it is?(backword compatibility) Or do I have to do some manual operations?
In other words, say I have a postgres database works with the latest version. Can I use the same database in other systems which run other supported versions of postgres (but not the latest)?
There is no supported way to downgrade PostgreSQL to a lower major release.
You will have to pg_dumpall with 9.5 and then try to install the dump in 9.2.
There will be error messages if the 9.5 dump uses features that were not present in 9.2 yet. In that case, edit the dump and fix it for 9.2.
Between major releases of postgresql, you will have to export your tables and database structure to older postgres version via pg_dump and pg_dumpall utilities. Then use the older version. This is the safest way.
If downgrading is done between minor releases, then just replacing the executables when the server is down and restarting the server will be sufficient, as the data directory remains unchanged between minor releases.