User profile for StephanieHerr

Hello, To answer your last question, the "trial period" for SQL Source Control will be 28 days. So, after installing the full release version, you will have 28 days to evaluate the software. Thank you! Stephanie M. Herr :-) Project Manager - SQL Source Control / comments

Hello, To answer your last question, the "trial period" for SQL Source Control will be 28 days. So, after installing the full release version, you will have 28 days to evaluate the software. Thank...

0 votes

We haven't seen this, but doing a quick Google search, it seems to be a permission thing with Subversion. It looks like you need to add the following line to your authz file. * = r Google hits: http://geekgok.blogspot.com/2009/01/svn ... dable.html http://sdesmedt.wordpress.com/2006/11/0 ... ubversion/ Please let us know if this doesn't work. Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments

We haven't seen this, but doing a quick Google search, it seems to be a permission thing with Subversion. It looks like you need to add the following line to your authz file. * = r Google hits:http...

0 votes

Hello, Just to note, SQL Source Control is still in an early access phase and we do not recommend using it on Production DBs. Your situation is kind of unique since you do not have a dev db... I don't understand exactly what you are trying to do. :-) It sounds like you are using Visual Studio and editing the CREATE script files directly. The whole purpose of SQL Source Control is that you can continue to work directly on your db within SQL Server Management Studio, so that you don't have to worry about the CREATE scripts and SQL Source Control generates them for you. If you do make a change in VS and commit it, then you should see this on the Get Latest tab and you can click the "Get Latest" button to update the db. What do you mean that you cannot "Get Latest?" Please be careful that the SQL syntax within the script is correct. This is why it is better to just work directly on the db. It's true that changes to the db do not automatically get committed to source control. This requires discipline from the db developer to commit the change. We would like them to supply a comment when commiting so others can understand why they made the change. SQL Source Control helps by placing blue indicators on the ObjExp, which reminds you that you have made changes that you haven't commited yet. You can use SQL Compare Pro to automatically check that your production db is at the version you expect it to be. This is retroactive, but allows you to see if any changes are made directly to prod that were not expected. These changes can then be applied back to your dev db and committed to source control if that's what is decided. I hope this helps! Please let me know if you are still having problems getting changes from TFS to your db. Thank you! Stephanie M. Herr :-) SQL Source Control - Project Manager / comments

Hello, Just to note, SQL Source Control is still in an early access phase and we do not recommend using it on Production DBs. Your situation is kind of unique since you do not have a dev db... I do...

0 votes

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

How can we help you today?

StephanieHerr

Comments