icelava.net

This matter has been eluding me for well over half a year, and I am so glad to finally discover where the fault lies in a Visual Studio [Team Edition for Database Professionals] database project, that causes SQLCMD variables checked in the Script.PostDeployment.sql file like IF '$(DeployTestData)' = '1'BEGIN /* INSERT TEST DATA */ /*Reporting ...

I thought this would be a very common style of deployment. Why write thousands of lines of INSERT when you can prepare CSV data in quicker fashion and use the BULK INSERT command? Surely developers would want that. Well, the Visual Studio team apparently did not think so. They must have been rushing to push the fourth Team Edition for Visual ...

My colleague hit a mysterious error message whenever she attempted to deploy the assembly compiled with our managed stored procedures to the SQL Server. An error occurred while gathering metadata from assembly 'Assembly.Name' with HRESULT 0x80004005. ProjectName It always failed at a particular stored procedure when it gives up, and she ...