Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Referencing DacPac file from different Server and Database

Referencing DacPac file from different Server and Database

Scheduled Pinned Locked Moved Database
databasehelpcsharpsql-servervisual-studio
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I Offline
    I Offline
    indian143
    wrote on last edited by
    #1

    Hi All, I have a DacPac file that is generated on a server, in which Views are using different Server references and I want to reference it in my Database project as a Database reference. When I do it, it is throwing following error, can anybody please help me in it, any sort of help, a suggestion, a link or a code snippet would be very helpful. I am generating the DacPac file from Management Studio and trying to reference it in the SSDT project, lets suppose if it is only because of the version mismatch between SSDT and Management Studio, how can we avoid this mismatch, I am using SQL Server 2008 R2, Visual Studio 2013 and SSDT 12.0, doesn any of these version matter. Any sort of help is greatly appreciated. And another important thing is my database View are referencing other database, when I went on to that database, the views in that db are referencing another database and when I went into that database the views in that are referencing an another db, like this it goes on, if referencing other dbs is the cause of error, then what can we do to resolve it in those situations. Thank you. The error is as below:

    'C:\Users\AleemA\Desktop\SHP.dacpac' is not accessible or is not a valid schema (.dacpac) file.

    Thanks in advance.

    Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."

    M 1 Reply Last reply
    0
    • I indian143

      Hi All, I have a DacPac file that is generated on a server, in which Views are using different Server references and I want to reference it in my Database project as a Database reference. When I do it, it is throwing following error, can anybody please help me in it, any sort of help, a suggestion, a link or a code snippet would be very helpful. I am generating the DacPac file from Management Studio and trying to reference it in the SSDT project, lets suppose if it is only because of the version mismatch between SSDT and Management Studio, how can we avoid this mismatch, I am using SQL Server 2008 R2, Visual Studio 2013 and SSDT 12.0, doesn any of these version matter. Any sort of help is greatly appreciated. And another important thing is my database View are referencing other database, when I went on to that database, the views in that db are referencing another database and when I went into that database the views in that are referencing an another db, like this it goes on, if referencing other dbs is the cause of error, then what can we do to resolve it in those situations. Thank you. The error is as below:

      'C:\Users\AleemA\Desktop\SHP.dacpac' is not accessible or is not a valid schema (.dacpac) file.

      Thanks in advance.

      Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."

      M Offline
      M Offline
      Mycroft Holmes
      wrote on last edited by
      #2

      A quick search and a little light reading and I get this information from http://sqlblog.com/blogs/jamie_thomson/archive/2014/01/18/dacpac-braindump.aspx[^] Dacpacs are used for deploying SQL Server objects to an instance of SQL Server It seems you are trying to reference it like a database rather than installing it to the server.

      Never underestimate the power of human stupidity RAH

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups