SQL Connect needs tosupport TFS check out, check out exclusive, and check in policies with regards to work items

When creating views/tables in Management Studio, we do not use the interface. We write straight t-sql in a new query window. We would like to have this option when using SQL Connect. Currently, you can do this if you use the "Edit file in project" option, but if you want to work against the database, SQL Connect forces you to use the table designer.

Currently, when you double click an object in source control it opens to modify it in the database. To edit the SQL file in project you must right click the object and select that option. It would be nice for the people who prefer to edit the script in the project first to be able to make the default double click actionto be "edit the SQL file in the project".

Would like the ability to select a template when creating a new object. For example, in Visual Studio, we have custom templates for different objects, such as procedures, functions, views. These templates contain place holders for things we want developers to remember to put in their scripts, such as header comments and certain permissions.

Currently, we have projects that use the same database, but I only want to pull out what I use, stored procedures, tables...

I don't need EVERY stored procedure

With multiple team members, it is important to know which objects are checked out and to be able to check out exclusively(prevent others from modifying). Plus i do not find an equivalent merge utility to that is available in Visual Studio when conflicts arise where you get to choose lines from either version to merge into the object.

It would be nice to be able to add a folder to the redgate sql connect project and set the folder so it is not compared to the database. We'd like to store useful and/or related queries that are often used in a particular database to source control. It would make sense to keep these scripts along side of the database in source control. Would like sql connect to essentially ignore it, but allow the addition of a folder and anything we want below that folder.

I use SQL Notifications in one of my database. This is creating SP like this one:

ALTER PROCEDURE [SqlQueryNotificationStoredProcedure-31560677-ebce-4d11-ad0d-5f3524379f90] AS BEGIN BEGIN TRANSACTION; RECEIVE TOP(0) conversation_handle FROM [SqlQueryNotificationService-31560677-ebce-4d11-ad0d-5f3524379f90]; IF (SELECT COUNT(*) FROM [SqlQueryNotificationService-31560677-ebce-4d11-ad0d-5f3524379f90] WHERE message_type_name = 'http://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer') > 0 BEGIN DROP SERVICE [SqlQueryNotificationService-31560677-ebce-4d11-ad0d-5f3524379f90]; DROP QUEUE [SqlQueryNotificationService-31560677-ebce-4d11-ad0d-5f3524379f90]; DROP PROCEDURE [SqlQueryNotificationStoredProcedure-31560677-ebce-4d11-ad0d-5f3524379f90]; END COMMIT TRANSACTION; END

Because these SP are recreated everytime users connects, you need to find a way of keeping these objects outside SQL Connect.

Attempted to View Data or enter the Table Designer in VS 2010 on a project and this message is thrown.

Tried synchronizing the database, which had no effect.

Running SQL Connect 1.0.1.1172 and VS 2010 Pro on a Win7 64 box.

Is support for VisualSVN forthcoming? We have no visual cues of what has changed inside Visual Studio.

Periodically, the information in my sql connect window doesn't match up with my output (SQL Connect) information.

i.e.
(SQL Connect Window )
SQL Connection - Last synchronized at 9:06:08 - 2 object changed

(Output Window - SQL Connect)
... 1 object changed....

I can't seem to find a constant way to reproduce the error, but I will provide more information if I find some.

Creating a new database project for a database that doesn't yet exist creates an empty folder in the solution directory. After creating the database i SSMS, a new database project cannot be added to the solution with the same name without first removing the directory created in the first failed attempt.

Suggested resolution; remove empty project directory when no new project was added to the solution or prompt and create database.

I don't easily find (I may be blind) the version number of the current Connect installation. Can you please show it when syncing.

Not sure if it has been mentioned, or if I have missed something, however a database diagrams window would be helpful, where one could create/define and /or delete joins and relationships which are then synchronised back to teh DB.

Question: Why is SQL Connect much better than a "normal" microsoft database project?

Need some good killer arguments to satisfy my boss...

I see the option to connect with SQL Source Control, but I don't have a RedGate.ssc file on my disk. I see the file is checked into the SVN Server though.

Running Windows 7 64-bit - perhaps I'm not looking in the right area?

Or will the 2 products work together? I like the idea of writing/modifying scripts directly in Visual Studio and the user interface is slick. However, it seems to be missing the concepts of filtering objects, linking static data, and creating migration scripts that SQL Source Control has. Also, how would deployments be done using this tool? I understand fairly well how continuous integration works with SQL Source Control using SQL Compare/Data Compare. But I have no idea how one would deploy database changes using this new tool.

The ability to filter by the db object's name. For example, I could right-click on the Tables folder and from the menu select eg 'Filter...' and give me a dialog where I could specify a filter for example, 'ABC%' would only show all tables beginning with 'ABC' on the RG DB project's tree.