none
Azure SQL Database와 로컬DB Datasync시 오류 RRS feed

  • 질문

  • 2년정도후 완성할 계획으로 프로젝트를 진행하고 있습니다.

    해서 로컬에는 Windows Server와 SQL SERVER 둘 다 모두 현상태 기준 가장 최신 상태인 2016으로 하고

    azure SQL Database와 datasync하는것을 테스트하고 있는데

    azure에서 동기화하려는 테이블과 컬럼들이 보여지지 않아 로그를 확인해보니

    Getting schema information for the databse failed with the exception
    "Failed to retrieve data for this request.
    Inner exception : Operation not supported on version 12.0 SqlAzureDatabase
    ....."

    이런 에러가 나옵니다.

    이 에러는 azure쪽 SQL Server쪽에서의 문제인지

    아니면 로컬서버의 2016서버 문제인지 모르겠네요.

    로컬쪽을 서버와 sql 모두 2012로 낮춘다면 에러가 안날까요?

    2년뒤면 2012로 사용하기에는 버전이 너무 낮을 것 같은데

    sql server 2016과 azure database와 datasync 성공하신 분 계신가요?

    2017년 8월 4일 금요일 오전 1:29

답변

  • 안녕하세요,

    다음 내용을 참고하여 주시기 바랍니다.

    This is known issue reported to us already. If you use non-default collation for your database, scripting individual objects will result in the error.

    We are working to address it in SQL Server 2012 SSMS service pack 1.  In the meantime, here are some workarounds:

     
    Scripting out objects
    =====================
    There are two potential workarounds
    Workaround 1:  use SQL Server 2012 management studio
     
    In SQL Server 2012 management studio, you can actually script all schemas if you use “Extract Data-tier application” (not “Export Data-tier application”).  “Extract data-tier application” only extract schema.  After you extract all the schema, you can get your table or procedure to use.  This will require SQL Server 2012 management studio.
     
    Workaround 2:  use SQL Server Data tools (SSDT)
    We SSDT is the tool that integrate with Visual Studio 2010 and 2012 (http://msdn.microsoft.com/en-us/data/tools.aspx).  If you have Visual studio 2010 or 2012, you can download the tool free.
    Once you install the tool, you will have option under “SQL Server Object Explorer” under “View” menu.
    You can right click on the table or procedure, choose “view code”. You can script out individual objects.
     
     
    Backup data
    =============
    Workaround 1: SqlPackage.exe: 
     
    you can download SQL Server data tools (http://msdn.microsoft.com/en-us/data/tools.aspx) which has sqlpackage.exe (http://msdn.microsoft.com/en-us/library/hh550080(v=vs.103).aspx). This tool allows you to backup or extract schema using command line parameters.  Here is an example, the following command line will export GreetTest database to a file called c:\temp\GreekTest.bacpac.   
     
    “C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\sqlpackage.exe”  /Action:Export /sdn:GreekTest /ssn:<servername>.database.windows.net /su:<username> /sp:password /tf:c:\temp\Test.bacpac 
     
    Workaround 2:   using Azure Storage with import/export to backup data
    You mentioned that there is charges involved.  From a few offerings (http://www.windowsazure.com/en-us/offers/ms-azr-0020p  and http://www.windowsazure.com/en-us/offers/ms-azr-0003p) we have, Azure Storage is included.  Can you elaborate a bit more on which offering that would incur extra charges?

    • 답변으로 표시됨 treefrog_s 2017년 8월 5일 토요일 오전 12:22
    2017년 8월 4일 금요일 오전 4:10
    중재자