How can we help you today? How can we help you today?
Chris Auckland
Activity overview Badges (0) Posts (7) Comments (611)

Comments

Sort by recent activity
Sorry for the slow reply. We're still looking into performance improvments for SQL Source Control, but I can give you a workaround which might help you in the mean time. The workaround is to disable the code that polls your database. This will mean that the blue indicators in the Object Explorer are often out of date, but it should reduce the load on your database server to acceptable levels. To apply the workaround, you will need to edit the 'RedGate_SQLSourceControl_Engine_EngineOptions' in your SQL Source Control configuration directory. This is either: C:\Users\<username>\AppData\Local\Red Gate\SQL Source Control 1 or C:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\SQL Source Control 1 depending on your operating system version. The following XML is an example of setting the polling frequency to '0'. This will mean that SQL Source control will not check for changes, but you can still manually perform the check if you hit 'refresh'. You might want to try different values between 0 and the defaults, until you have an acceptable performance. &lt;?xml version="1.0" encoding="utf-16" standalone="yes"?&gt;&lt;!----&gt;&lt;EngineOptions version="2" type="EngineOptions"&gt;&lt;DefaultTraceMinimumInterQueryTimeInMillis&gt;0&lt;/DefaultTraceMinimumInterQueryTimeInMillis&gt;&lt;SysObjectsMinimumInterQueryTimeInMillis&gt;0&lt;/SysObjectsMinimumInterQueryTimeInMillis&gt;&lt;SysTypesMinimumInterQueryTimeInMillis&gt;0&lt;/SysTypesMinimumInterQueryTimeInMillis&gt;&lt;DefaultTraceMinimumRequestedInterQueryTimeInMillis&gt;0&lt;/DefaultTraceMinimumRequestedInterQueryTimeInMillis&gt;&lt;/EngineOptions&gt; THE v1 DEFAULT VALUES ARE: 25000 DefaultTraceMinimumInterQueryTimeInMillis 2500 SysObjectsMinimumInterQueryTimeInMillis 3500 SysTypesMinimumInterQueryTimeInMillis 5000 DefaultTraceMinimumRequestedInterQueryTimeInMillis I hope this helps. / comments
  1. Community
  2. SQL Source Control Previous Versions
  3. SQL Server 2005 Processes SLOOOOW
Sorry for the slow reply. We're still looking into performance improvments for SQL Source Control, but I can give you a workaround which might help you in the mean time. The workaround is to disabl...
0 votes
Is it possible to get a UI for this so we can search for WIs or by user, etc... Hi AdamR, Can you go into a little bit more detail with regards to the kind of UI you would like? Is there any functionality that you're looking for that Team Explorer doesn't provide, or are you looking for a more convenient interface than using Team Explorer? / comments
  1. Community
  2. SQL Source Control Previous Versions
  3. Support for Team Foundation Server Work Items
Is it possible to get a UI for this so we can search for WIs or by user, etc... Hi AdamR, Can you go into a little bit more detail with regards to the kind of UI you would like? Is there any f...
0 votes
Would it be possible to add tags for other standard states such as "Closed" as well? Hi JeffJ, I've added a feature request for this: SOC-1513 / comments
  1. Community
  2. SQL Source Control Previous Versions
  3. Support for Team Foundation Server Work Items
Would it be possible to add tags for other standard states such as "Closed" as well? Hi JeffJ, I've added a feature request for this: SOC-1513
0 votes
Thanks for your post. SQL Compare will compare the column level collations by default. When you look at the results grid after a comparison, select the table object from the top grid to view any collation differences in the 'SQL differences' pane at the bottom of the screen. You can ignore the collations on a column if you wish by checking the project option Ignore > Collations. SQL Compare won't show you the collation for the entire database as it will only compares at the object level. I hope this helps. / comments
  1. Community
  2. SQL Compare Previous Versions
  3. COMPARE to include collation info ?
Thanks for your post. SQL Compare will compare the column level collations by default. When you look at the results grid after a comparison, select the table object from the top grid to view any co...
0 votes
This has now been fixed in SQL Compare 10.1 and can be downloaded through Help | 'Check for Updates' / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Comparison gaffe with data compression
This has now been fixed in SQL Compare 10.1 and can be downloaded through Help | 'Check for Updates'
0 votes
Thanks for your post. SQL Compare isn't really a replication technology or a replacement for replication, but if you want to use it just to make a copy of certain database objects I would say that the main advantage of using SQL Compare over SQL Server replication is that you can quite easily get some feedback (using the GUI, or outputting a report) that the replication is successful. SQL Compare is also much easier to configure, but you will need to schedule it using another process such as a Windows Scheduled task. Unless you want to use xp_cmdshell. I hope this helps. / comments
  1. Community
  2. SQL Compare Previous Versions
  3. SQL Compare versus sql server replication
Thanks for your post. SQL Compare isn't really a replication technology or a replacement for replication, but if you want to use it just to make a copy of certain database objects I would say that ...
0 votes
Unfortunately we don't have any code that considers the dependencies between udts. It works with a live database as we base the dependency on the order they're created, and the UDDT has to be created before the UDTT that references it. With scripts, we're not so lucky as each type has it's own file, and the files are evaluated in alphabetical order. We will be able fix this, but it isn't something we can patch and will need to wait for a full release. I think the only workaround will be to make sure you sync the UDDT first, and then everything else. / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Deadlock when syncing
Unfortunately we don't have any code that considers the dependencies between udts. It works with a live database as we base the dependency on the order they're created, and the UDDT has to be creat...
0 votes
Thanks for your post. How do I not compare the execute as on triggers and procs? This isn't possible with the current version, but we might be able to add an option. Is it common for you to have the same stored procs executed under a different security context on different databases? I also am looking for how not to compare FOR versus AFTER on the trigger keyword. Again we could have an option, but I would think this is a very significant difference that you would always want synchronized. Could you give me an example of a situation where you would want to ignore this difference? / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Don't compare EXECUTE AS
Thanks for your post. How do I not compare the execute as on triggers and procs? This isn't possible with the current version, but we might be able to add an option. Is it common for you to have...
0 votes
I was just going to respond to this, and I noticed your update. You can also exclude the column by unchecking the PK column from 'Columns In Comparison' on the 'Tables & Views' tab / comments
  1. Community
  2. SQL Data Compare Previous Versions
  3. Can't generate insert scripts without Primary Key
I was just going to respond to this, and I noticed your update. You can also exclude the column by unchecking the PK column from 'Columns In Comparison' on the 'Tables & Views' tab
0 votes
Thanks for your post. You can exclude the PK column from the synchronization, but only if you don't use it as the comparison key in the project. By default, SQL Data Compare will use the primary key as the comparison key, but you can set up your own custom key, or custom composite key to use instead. Once you do this, you can exclude the PK column. You can set this on the 'Tables & Views' tab of project configuration. I hope this helps. / comments
  1. Community
  2. SQL Data Compare Previous Versions
  3. Can't generate insert scripts without Primary Key
Thanks for your post. You can exclude the PK column from the synchronization, but only if you don't use it as the comparison key in the project. By default, SQL Data Compare will use the primary ke...
0 votes
Total activity
1052
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
434