An error occurred while attempting to deploy project scripts Sqlcmd: Error: Syntax error at line xxx
atzino
Posts: 6 New member
I'm somewhat new to Redgate. I've used it for version control with a new small database, but I'm attempting to import an existing database into a Database Solution in Visual Studio 2015. When I click the Deploy Project button, my SQL Script runs, but I get the following error message:
An error occurred while attempting to deploy project scripts:
Sqlcmd: Error: Syntax error at line 182867 in file 'C:\tfs\Database Projects\obj\Debug\My! DB.sql
Each time I click the Deploy Project button, the line number containing the error changes. Any idea where I'm going wrong? Any help is much appreciated.
An error occurred while attempting to deploy project scripts:
Sqlcmd: Error: Syntax error at line 182867 in file 'C:\tfs\Database Projects\obj\Debug\My! DB.sql
Each time I click the Deploy Project button, the line number containing the error changes. Any idea where I'm going wrong? Any help is much appreciated.
Tagged:
Answers
How are you creating the file and deploying it? There's a Deploy with SQL Compare, but I don't see a Deploy Project button, unless I'm looking somewhere else. Can you provide more details about what you're doing to get to this point? That folder structure looks funny as well. Is this a SQL Source Control project, or are you trying to connect to a database project from SSDT/Visual Studio in TFS?
Thanks for your clarification.
Do you use ReadyRoll. Can you please share a screenshot where we can see the error?
Thanks.
Tianjiao Li | Redgate Software
Have you visited our Help Center?
C:\Program Files (x86)\MSBuild\ReadyRoll\ReadyRoll.Data.Schema.SSDT.targets(440, 5): An error occurred while attempting to create a patch script: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)