Paul Stephenson

My feedback

  1. 420 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  SQL Source Control » Static Data  ·  Flag idea as inappropriate…  ·  Admin →
    Paul Stephenson commented  · 

    Good spot Graham. I've merged the two suggestions now.

  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Paul Stephenson commented  · 

    Hi Rusty, the checkbox at the top of the column of checkboxes acts as a global switch. Does this do what you want?

  3. 210 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →

    This is now available in the full release of SQL Source Control, http://www.red-gate.com/products/sql-development/sql-source-control, but it is still a beta feature.

    SQL Source Control can link databases to the most recent version of Microsoft database projects (those folders containing a .sqlproj file).

    It’s important to stress that this is a beta-quality feature, and as such it is only intended for experimental use. In particular, we are aware of some limitations regarding database-level extended properties, permissions and CLR assemblies. If you encounter these limitations or any other problems with this new SSDT compatibility, please let us know by using the Feedback link in SQL Source Control or contacting support@red-gate.com.

    Paul Stephenson commented  · 

    @Anonymous: Are you using SQL Connect at the moment for connecting to a Visual Studio database project? Have you already tried using SQL Source Control instead? If so, what issues (if any) remain before you would be happy to use SQL Source Control as your primary tool for interacting with the VS database project?

    To move the support out of beta status we would like feedback to confirm that it meets your needs in real-world situations -- and if it doesn't, what those limitations are so that we can look at addressing them.

    Paul Stephenson commented  · 

    @Peter: Improving support for branches in SQL Source Control is high up on our priority list and we'll be looking at it soon. For the moment, a workaround is to switch branches using your normal source control tool. Then in SQL Source Control, do a Get Latest to pick up differences in the new branch. After that, on the Commit Changes tab, right-click and Undo Changes. These steps should make the database match whatever is in the filesystem's new branch.

  4. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Prompt » Find invalid objects  ·  Flag idea as inappropriate…  ·  Admin →
    Paul Stephenson commented  · 

    As a workaround, you can copy and paste the list into a spreadsheet. Click on a result, press Ctrl+A or Shift-click to select them all and then right-click and Copy. Paste into your favourite spreadsheet application -- SQL Prompt also adds the database name in case you want to add rows for more than one database in the same sheet.

Feedback and Knowledge Base