User profile for StephanieHerr

Hello, It looks like we may be having problems parsing your table name since it includes a $. Would you be able to email SqlSourceControlSupport@red-gate.com the CREATE script for this table so that we can try to reproduce the problem here? Thanks for your help! Stephanie M. Herr :-) SQL Source Control Project Manager / comments

Hello, It looks like we may be having problems parsing your table name since it includes a $. Would you be able to email SqlSourceControlSupport@red-gate.com the CREATE script for this table so th...

0 votes

Hi Wesley, This move sounds like it might be similar to branching, which we currently don't support... We'll look into a workaround or a fix. Our internal reference number for this issue is SOC-922. Thank you for submitting the issue from SQL Source Control and following up with this forum posting. The details you provided have been very helpful. Thanks again! Stephanie Herr / comments

Hi Wesley, This move sounds like it might be similar to branching, which we currently don't support... We'll look into a workaround or a fix. Our internal reference number for this issue is SOC-9...

0 votes

Emailed VladimirL directly to try to make sure the "too long" exception is fixed and work through this new issue of circular dependencies. / comments

Emailed VladimirL directly to try to make sure the "too long" exception is fixed and work through this new issue of circular dependencies.

0 votes

We have a release which should fix this, http://downloads.red-gate.com/EAP/SQLSo ... .3.2.2.exe. The email will be going out later today, but I wanted to get this to you ASAP! Please let us know if this works and you can continue using SQL Source Control or if you hit any other issues. Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments

We have a release which should fix this, http://downloads.red-gate.com/EAP/SQLSo ... .3.2.2.exe. The email will be going out later today, but I wanted to get this to you ASAP! Please let us know i...

0 votes

A fix will be available early next week. This is the week beginning April 19th. I hope this is ok. / comments

A fix will be available early next week. This is the week beginning April 19th. I hope this is ok.

0 votes

Thank you for reporting this issue. We are working on a fix for this. We should have another release next week. I hope you can wait until then... / comments

Thank you for reporting this issue. We are working on a fix for this. We should have another release next week. I hope you can wait until then...

0 votes

Thank you for letting us know about this issue. Our internal reference number is SOC-900 and we are currently looking into this. / comments

Thank you for letting us know about this issue. Our internal reference number is SOC-900 and we are currently looking into this.

0 votes

Hi, We are currently working on this issue. It's surprising how many people have # in their db object names... :-) Would you be able to email us a copy of the dbo.USPEmp# to SqlSourceControlSupport@red-gate.com? This way, we could recreate the exact issue that you are having and test it internally. This will only be used for our internal test purposes. Our internal reference number is SOC-599. Thanks for your help! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments

Hi, We are currently working on this issue. It's surprising how many people have # in their db object names... :-) Would you be able to email us a copy of the dbo.USPEmp# to SqlSourceControlSuppo...

0 votes

We have been able to reproduce the GO alias problem here. Would it be possible to use a different alias for now? / comments

We have been able to reproduce the GO alias problem here. Would it be possible to use a different alias for now?

0 votes

1) You must have Team Explorer installed on your client machine that is using SQL Source Control through SQL Server Management Studio (SSMS). You will probably want to install Team Explorer 2008. (If Team Explorer is NOT installed, then you will see a missing prerequisite message when you select the TFS radio button when linking your db to source control.) 2) You should create an emtpy "Database" folder in your TFS repo. To do this: - Open Visual Studio - Select View > Team Explorer - Add an existing Team Project - Connect to a Team Foundation Server - Double click on the "Source Control" folder, this will open the "Source Control Explorer" - Right click on the tree and select Get Latest Version - Navigate to where you want to create your database folder - Right click in the main explorer window, not the tree - Select New Folder - Give your new folder a name - Right click on the folder and select "Check In Pending Changes..." - Add a comment and click Check In 3) Now back in SSMS, right click on a db and select "Link DB to source control...." 4) On the setup tab, click the "Create new link to source control..." link 5) Select TFS if this is not the default. (SQL Source Control will remember the last source control system you linked to.) 6) Select or enter the TFS Server URL. 7) If you have Team Explorer 2008 installed, then you can Browse the Team Foundation Server and select the empty folder you created. 8) Click "Create link" 9) Click on the "Commit changes" tab. Enter a comment like "initial db baseline" or "initial commit" and click "Commit." Your db is now linked to source control and your initial commit is completed. Now you can have other users link their db to the same central repo. You're ready to start making changes to your dev db and once you're happy with the change, right-click on the db or node under the db and select commit changes. This brings you back to the commit changes tab. Enter a comment and commit your changes. I hope this helps! / comments

1) You must have Team Explorer installed on your client machine that is using SQL Source Control through SQL Server Management Studio (SSMS). You will probably want to install Team Explorer 2008. ...

0 votes

How can we help you today?

StephanieHerr

Comments