Crispy Holiday
Crispy Holiday

Reputation: 472

Visual studio 2013 database publish do nothing

I'm trying to publish a DB project in Visual Studio 2013 Professional and the "Publish" button do nothing. In project properties I checked "Create script (.sql file)". I right click the project name in solution explorer > Publish... > Load Profile (a profile that works for my colleagues) > Publish

Nothing Happens, not an error, warning or anything (same with "Generate Scripts" button). Visual studio error logs say nothing and I tried to restart the PC, Visual studio and SQL server.

Thank you!

Upvotes: 11

Views: 2597

Answers (5)

Nana-One
Nana-One

Reputation: 1

I found that having an Azure Queue or Blob Storage opened in Visual Studio Professional 2015 meant that clicking Publish did nothing and I couldn't close the application. After closing those windows which I had launched from the Cloud Explorer, I had to click Publish once again to kick it off. A strange bug.

Upvotes: 0

SvenAelterman
SvenAelterman

Reputation: 1662

If you have an Azure Cloud Explorer window open in Visual Studio (could be table, blob or queue), that leads to the Publish of an SSDT project hanging.

Close the window and start a new Publish operation. It may take a little longer than usual but eventually that will progress and you'll be able to close Visual Studio as normal.

Thanks to Noel Abrahams for his comment that led to this answer.

EDIT: putting it here as an answer so that it can be more easily found but credit goes to Noel.

Upvotes: 3

Giles Roberts
Giles Roberts

Reputation: 6883

For me publishing the database project to a new sql server database with a different name allowed the publish to proceed. Once I'd done that I was then able to publish to the original database again.

Upvotes: 0

Alexey Kuptsov
Alexey Kuptsov

Reputation: 86

I cloned the solution from VCS to a new directory and only this helped.

Other symptoms that I had with this issue:

  • While editing a table .sql script, Design pane didn't work.
  • Integrated Security=True; was set in my publishing profile. So Rhumborl's answer is not about my case.
  • If the solution folder is copied to another machine the issue is reproduced there too.

I tried to Clean Solution before re-cloning, but it didn't work.

Upvotes: 0

Rhumborl
Rhumborl

Reputation: 16609

Found a fix on the MS Connect site.

In my publish profile I had set the connection string as so:

<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=SSPI;</TargetConnectionString>

According to the comments on Connect, it doesn't like Integrated Security=SSPI. Instead you should use Integrated Security=True;:

<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=True;</TargetConnectionString>

Then it all works fine.

Upvotes: 2

Related Questions