User profile for Chris Auckland

Can you try upgrading to SQL Compare 10.4? If you get the same behavior on the latest, I'll create a similar project and see if I can recreate the problem. / comments

Can you try upgrading to SQL Compare 10.4? If you get the same behavior on the latest, I'll create a similar project and see if I can recreate the problem.

0 votes

try it without the .* syntax. I'm not sure wildcards are supported in that way. e.g. /include:View /exclude:Role / comments

try it without the .* syntax. I'm not sure wildcards are supported in that way. e.g. /include:View /exclude:Role

0 votes

Sorry my fault. It's IncludeDependencies and that's one of the default options, so your original command should have worked :S Can you post your original command, the options switch should have a : rather than an = sign. e.g. /options:option1,option2 / comments

Sorry my fault. It's IncludeDependencies and that's one of the default options, so your original command should have worked :S Can you post your original command, the options switch should have a :...

0 votes

Thanks for your post. I would imagine the problem is that another object in your project had a dependency on the role and it's being brought back in. By default, we bring back dependent objects, as they're probably required or it's likely the script will fail or it will leave your database in an inconsistent state. If you want to ignore dependencies, you can use the option 'IgnoreDependencies' I hope this helps. / comments

Thanks for your post. I would imagine the problem is that another object in your project had a dependency on the role and it's being brought back in. By default, we bring back dependent objects, as...

0 votes

Thanks for your post. SQL Prompt 5 should be able to co-exist with the native intellisense. There are a few features (like parenthesis matching) that the native tool supports that we don't, so they can both be enabled. However, the candidate list pop-up should only be enabled for one of them, or they will interfere with each other. It sounds like for some reason Tools > Options > Text Editor > Transact SQL > General > Auto list members is still enabled, which would cause the native list to pop-up as well. The main advantage over the native intelisense is the additional formatting and non-code completion features: http://www.red-gate.com/products/sql-de ... ure-matrix There is also advantages in the way SQL Prompt makes suggestions for code completion, but I have to say I'm not entirely sure how sophisticated the native intelisense has become to confirm if we still have an advantage in that area. I hope this helps. / comments

Thanks for your post. SQL Prompt 5 should be able to co-exist with the native intellisense. There are a few features (like parenthesis matching) that the native tool supports that we don't, so they...

0 votes

Thanks for your post. I'm afraid we don't have support for formatting FETCH NEXT statements, which is why the behavior isn't completely predictable. I've added you as another vote for SP-3019. / comments

Thanks for your post. I'm afraid we don't have support for formatting FETCH NEXT statements, which is why the behavior isn't completely predictable. I've added you as another vote for SP-3019.

0 votes

Thanks for your reply. The good old turn it off and on again trick to the rescue. I hope it behaves from now on. / comments

Thanks for your reply. The good old turn it off and on again trick to the rescue. I hope it behaves from now on.

0 votes

Thanks for your post, and sorry you're having trouble with the migration scripts. In order for SQL Source Control to consider the migration script, the database revisions need to be correct in the database level extended properties, and the database needs to be linked to the exact same repository. We don't currently support cross branch migration scripts, so if something doesn't match up, then we err on the side of caution and ignore it. Can you take a look at 'CompassionWeb 11234 to 11466.migrationScript' and also at the linked database's extended properties and see if the repository locations all match up? / comments

Thanks for your post, and sorry you're having trouble with the migration scripts. In order for SQL Source Control to consider the migration script, the database revisions need to be correct in the ...

0 votes

Thanks for your post. I've seen this sort of thing occur with some minor corruptions in the database schema before. The most recent one that springs to mind was related to extended properties. When you receive the error, are you able to submit the error report with your email address? That should hopefully give us a clue to where the process is failing. / comments

Thanks for your post. I've seen this sort of thing occur with some minor corruptions in the database schema before. The most recent one that springs to mind was related to extended properties. When...

0 votes

Thanks for your post. Which version of SQL Server are you using? This doesn't appear to happen when I tested it with SQL 2008 and SQL 2012. Are you restoring using native SQL or something else? What does sp_who2 show you for the connection to the database you're trying to restore? / comments

Thanks for your post. Which version of SQL Server are you using? This doesn't appear to happen when I tested it with SQL 2008 and SQL 2012. Are you restoring using native SQL or something else? Wha...

0 votes

How can we help you today?

Chris Auckland

Comments