Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run db script doesn't work with GO statements #1393

Closed
andyking32 opened this issue Oct 3, 2016 · 3 comments
Closed

Run db script doesn't work with GO statements #1393

andyking32 opened this issue Oct 3, 2016 · 3 comments

Comments

@andyking32
Copy link

If I use the Fake.SQL.SqlServer runScript method, it won't work if you have Go statements. I get an error message stating Microsoft.SqlServer.BatchParserClient.dll can't be found.

I can resolve this by dropping v12 of Microsoft.SqlServer.BatchParserClient.dll and microsoft.sqlserver.batchparser.dll into the tools folder.

I'm currently using 4.40.0 and see the following SqlServer dlls in the tools folder:
Microsoft.SqlServer.ConnectionInfo.dll
Microsoft.SqlServer.ConnectionInfoExtended.dll
Microsoft.SqlServer.Management.Sdk.Sfc.dll
Microsoft.SqlServer.Smo.dll
Microsoft.SqlServer.SmoExtended.dll
Microsoft.SqlServer.SqlClrProvider.dll
Microsoft.SqlServer.SqlEnum.dll

However, I see in 4.41 that some dlls are now no longer there and you have just three:
Microsoft.SqlServer.ConnectionInfo.dll
Microsoft.SqlServer.Management.Sdk.Sfc.dll
Microsoft.SqlServer.Smo.dll

Not sure what the reason is for the difference between 4.40.0 and 4.40.1. I was going to submit a PR added the two new dlls above.

Please advise how to proceed on this.

@matthid
Copy link
Member

matthid commented May 7, 2017

Are we missing an dependency? was this resolved in the mean time?

@matthid matthid added the bug label May 7, 2017
@andyking32
Copy link
Author

Noone ever responded so i didn't submit the PR. You need the two dlls mentioned above in order to be able to run go commands.

@matthid
Copy link
Member

matthid commented May 13, 2017

See #1377. No idea if we can revisit the decision to support SQL Server 2008 R2...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants