Cross database variable

Question

I've imported an old database into datadude and built it to get the .dbmeta file, and then imported that into my main database project and referenced it, which works fine. I've assigned the database variable $(liveops) to point to the database (liveops_dev) and have been using it in my stored procedures which is working fine, and all the variables are getting converted correctly into the temp database name in the design time database. However, when I perform a schema compare against my staging database and write the updates, the variable names are left intact in the update script, even though the source window shows it converted correctly.

 

I've taken a screenshot and dumped it at:

http://www.cryptpad.com/dbproerror.jpg

 

Anyone know what's wrong? I may, as usual, be doing something silly!

Answer 1

I reproduced what you are seeing. And at this point, I feel it could be some issue with the product. I will investigate more and let you know what I find.

 

- Sachin Kumar (MSFT)

Answer 2

Schema compare update script is missing the "etvar" statement for declaring the variable.

Certainly an issue with the product, not known before this.

 

Please let us know if it is blocking you at this point. Although the workaround is to export the script to the editor, and modify it by adding the following.

etvar liveops "liveops_dev"

 

or

use the deploy script for doing the updates to the database.

 

Sachin Kumar (MSFT)

 

Answer 3

wierd emoticons. I meant [colon]setvar.

Answer 4

Hello,

OK, it is blocking us a bit, but as you say, there are workarounds. Do you want me to log this on connect?

Answer 5

Please log this on the connect site.

Thanks,

-GertD

 

Answer 6

Done. Feedback ID 306660

Answer 7

Is there any progress on this issue? Is it possible to get a hotfix, and is the fix to this issue intended for another service release/power tools release?

 

Answer 8

Right now this will be fixed in VS2008 SP1.

-GertD

 

Answer 9

 

What about vs2005?

Answer 10

Here is a functional work around that someone posted using a post build event and vbs script to edit the .sql file

 

http://topxml.com/rbnews/XML/re-69920_DataDude-Annoyance-13--Project-variables-omitted-from-output-script-.aspx

 

It took me hours to find this work around. MS please patch this in VS2005 DbPro.....

Answer 11

One of my fellow developers just came up with the zing "DataDud" after finding out about this bug. Ahh good times.

Answer 12

The hell? The connect bug has been changed to "Resolved (Not Reproducible)". Is that in error and it's been resolved due to being fixed, or can MS not reproduce this? Everyone else can

 

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=306660

Answer 13

As far as I know it was fixed in VS 2008 SP1 Beta. Let me know if you tried it and still see the issue.