• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Problem uploading Database. Error [Microsoft][ODBC SQL Server Driver][SQL Server][Ms

F

frozensphere

Guest
Hello Parallels Support Team,

I am experiencing problem restoring database.

Procedure:

st Attempt database restore not successful:

Procedure:

Logged onto Plesk Control Panel Cp4:
On domain domainexample.com
proceeded to Databases - > Database Backup Repository -> Upload File:
database_example.bak

Click OK to restore backup:

Error: dbbackup failed: Unable to restore database 'database_example'
[Microsoft][ODBC SQL Server Driver][SQL Server]The query uses non-ANSI outer join operators ("*=" or "=*"). To run this query without modification, please set the compatibility level for current database to 80, using the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN). In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes.


I have gathered information on http://itdunya.com/archive/index.php/t-80446.html about the problem, but this would help using the backend.

Is there a solution for fixing this problem through Plesk?

Please could you assist.

Thanx

EJI


------------------------------------------------------
Plesk Control Panel Windows 8.6
OS: Windows Server 2003 Sp1 n Sp2 installed.
MS SQL: SQL Server 2008 R2.

database: database_example
Database User: database_user
--------------------------------------------------------
 
I've also been experiencing this error under Plesk 8.6 against MS SQL Server 2008 database instances.

It doesn't matter if I use a backup that I upload, or if I try to restore a backup made via Plesk. That is, I can create a database, add a user, choose "Backup Now", and create the backup without issue, but if I then try to restore that backup, the restore fails with the same error that the OP receives.

That suggests that the backup file is not causing the problem, because, I assume, there cannot be any version incompatibilities if the backup is produced on the same server, on the same day, as the restore is attempted.

I did find http://forum.parallels.com/showpost.php?p=349120&postcount=2
Which suggests that MSSQL 2008 is not supported under Plesk 8.6.

I then checked the release notes for 8.6, here:
http://download1.parallels.com/Plesk/Plesk8.6/Windows/8.6.0/plesk_8.6.0_build080722.15.htm#6

and 9.0, here:
http://download1.parallels.com/Plesk/PPP9/Windows/9.0.1/plesk_9.0.1_build090128.13.htm#6

And it seems that support for MSSQL 2008 is only officially added in 9.0.

I'm not a SQL or Plesk Admin, but based on the error, I'm guessing that Plesk is firing (or calling a process that fires) a SQL command to perform (or as part of) the restore process, and that command uses non-ANSI outer join operators... Hence the fail and error.

Can Parallels offer any guidance on this? Is there a patch for 8.6, or possibly a Plesk feature that will allow an Admin to modify any SQL command that might be causing the problem? Or is the only fix an upgrade to 9.0 or higher?

Does the behaviour vary by Windows/IIS version?

Does the error get resolved if you set COMPATIBILITY_LEVEL as per the error message guidance?
 
Back
Top