Comments
Sort by recent activity
Did you commit the minor changes before you attempted the 'get latest' on the second database?
Also, could you check the database level extended properties of the second database and make sure the revision is later than both the migration scripts? It's this value that SQL Source Control checks to see if a migration script should be applied. / comments
Did you commit the minor changes before you attempted the 'get latest' on the second database?
Also, could you check the database level extended properties of the second database and make sure the ...
Sorry for the delay. The support ticket that we had open didn't get reactivated after you last replied in November! I'm really sorry about that. It's open now. / comments
Sorry for the delay. The support ticket that we had open didn't get reactivated after you last replied in November! I'm really sorry about that. It's open now.
Thanks for the scripts.
I'll try to reproduce the issue and let you know what I find. / comments
Thanks for the scripts.
I'll try to reproduce the issue and let you know what I find.
Thanks for your post.
It sounds like a bug if it's missing a dependency and not dropping the filtered index.
Would you be able to post or PM me the complete DDL for the object so I can try and replicate the problem? / comments
Thanks for your post.
It sounds like a bug if it's missing a dependency and not dropping the filtered index.
Would you be able to post or PM me the complete DDL for the object so I can try and repl...
Thanks for your post.
I've tested this out and can see what you mean. I think it happens because the square brackets are special characters and need escaping. I tried adding the escape characters, and that seemed to fix it for me. Can you try: /include:StoredProcedure:\[myStored Procedure\] /include:StoredProcedure:\[MyStoredProcedure\]
/ comments
Thanks for your post.
I've tested this out and can see what you mean. I think it happens because the square brackets are special characters and need escaping. I tried adding the escape characters, ...
Thanks for your post.
We would recommend that you you SQL Compare to deploy a database revision to an Azure database.
Are you using Azure as a development server? We would normally recommend users to develop locally, and then to deploy to Azure rather than develop directly on an Azure database. / comments
Thanks for your post.
We would recommend that you you SQL Compare to deploy a database revision to an Azure database.
Are you using Azure as a development server? We would normally recommend users ...
Problem 2 looks ok with the latest version too.
To test:
1) Added the following to DB1
EXEC sys.sp_addextendedproperty @name=N'MS_Description', @value=N'Configuration values for the Log File Acquisition System. Set as of 2012-09-21:
Entity Attribute Value
========= ======== ==========
LogFileArchive FileDirectory c:\NovarArchive
LogFileInput FileDirectory c:\Novar
LogFileInput FileExtension .LG0
Transfer StartDate 1/1/2012' , @level0type=N'SCHEMA',@level0name=N'dbo', @level1type=N'TABLE',@level1name=N'Test'
GO
2) Comitted to SVN repo
3) Did a 'get latest' from DB2
4) scripted out the extended property from DB2 EXEC sys.sp_addextendedproperty @name=N'MS_Description', @value=N'Configuration values for the Log File Acquisition System. Set as of 2012-09-21:
Entity Attribute Value
========= ======== ==========
LogFileArchive FileDirectory c:\NovarArchive
LogFileInput FileDirectory c:\Novar
LogFileInput FileExtension .LG0
Transfer StartDate 1/1/2012' , @level0type=N'SCHEMA',@level0name=N'dbo', @level1type=N'TABLE',@level1name=N'Test'
GO
/ comments
Problem 2 looks ok with the latest version too.
To test:
1) Added the following to DB1
EXEC sys.sp_addextendedproperty @name=N'MS_Description', @value=N'Configuration values for the Log File Acquis...
Sorry for the delay.
This is fixed in the next update to SQL Source Control (any build > 3.1.0.4731).
It looks like there was an issue with the polling query we used, so certain changes didn't show up. Incidentally, if you added the extended property through SSMS, the indicator wouldn't show up until you refresh either, so it wasn't just external modifications causing the problem.
Thanks for taking the time to report this. / comments
Sorry for the delay.
This is fixed in the next update to SQL Source Control (any build > 3.1.0.4731).
It looks like there was an issue with the polling query we used, so certain changes didn't show...
I'll take a look at this, but I think it's more a SQL Source Control problem.
Are you using the shared or dedicated development model? / comments
I'll take a look at this, but I think it's more a SQL Source Control problem.
Are you using the shared or dedicated development model?
This seems to be an issue with the query we use to check for changes. It seems to be picking up on all sorts of system objects that it should really filter out.
We have had this and a few other problems with the 3.1 release, so we've actually now pulled it from the website until we fix these issues with the shared model.
I would recommend downgrading to version 3.0 for the time being: http://downloads.red-gate.com/checkforu ... 3.4214.exe
Sorry for the inconvenience. / comments
This seems to be an issue with the query we use to check for changes. It seems to be picking up on all sorts of system objects that it should really filter out.
We have had this and a few other pro...