User profile for rdaunce

I'm just another forum user, so I can't update anything. I'm sure someone at Red Gate reviews these, though. I haven't seen the SQL Prompt slow cache message recently, but I know what you are talking about. SQL Prompt runs queries behind the scenes that query database schema and metadata. The results of these queries are cached on your local computer and SQL Prompt uses that local cache when it needs any of that information. If those initial queries are taking longer than expected then the error message is displayed. If you were seeing that message prior to your issue then that might be a symptom of resource utilization or blocking issues on the SQL Server instance. If your issue was resolved with the command you ran then it was likely caused by a bad (resource intensive) plan in plan cache that SQL Server maintains and stores on the SQL Server instance. This is a different cache and is not related to the SQL Prompt cache on your local computer. The command you ran is not specific to SQL Prompt or Red Gate - it's a SQL Server command. If you run it with no parameters that target a specific cached object then it will remove everything from the plan cache on the SQL Server instance you are connected to. It should be used with caution, especially it in a production environment, unless you understand the what it does and the potential issues it might cause. The best way to handle your situation would have been to identify the bad plan(s) and only remove the specific plan from the cache. / comments

I'm just another forum user, so I can't update anything. I'm sure someone at Red Gate reviews these, though.I haven't seen the SQL Prompt slow cache message recently, but I know what you are talki...

0 votes

PE001 matches a SQL Prompt Code Analysis rule - Schema name for procedure is not specified I haven't seen a Code Analysis rule prevent execution of anything, though. It normally just displays a warning. There may be a setting that I'm not familiar with that can prevent a query from running if there is a Code Analysis issue. Does the PE001 message in the Messages window as an error after trying to run the query or is it showing in a different way (tooltip, pop-up, etc.)? / comments

PE001 matches a SQL Prompt Code Analysis rule - Schema name for procedure is not specifiedI haven't seen a Code Analysis rule prevent execution of anything, though. It normally just displays a war...

0 votes

Thanks for confirming that there was a change in behavior. My specific use case is cloning the working version in a pre-commit hook on the SQL Source Control repository. Once the clone is made, the pre-commit hook can perform validation and other operations can on the clone without unwanted side effects in the actual git repository. For example, I can validate that naming conventions are followed, or that consistent formatting is applied. If the hook identifies and corrects something, it copies it back to the original repository and the updated version is committed. Almost all of our per-commit hook script can be work on using a copy of the contents of the directory instead of having SQL Data Compare create the script folder. The one thing copying doesn't handle is applying consistent ordering of static data in the cloned version's creation scripts. In the scripts created by SQL Source Control, the order of the insert statements is inconsistent. In a commit to SQL Source Control involving static data, the commit frequently moves unchanged rows to different locations in the creation script and moves updated rows to the top of the creation script. There are many other forum and user-voice posts about SQL Source Control Static Data ordering inconsistencies and the issues it causes. The inconsistent ordering makes for extremely difficult merge conflict resolution and it makes it difficult to identify what has actually changed when viewing diffs on the git repository. These issues make it easy to for one developer to accidentally revert static data changes made by another developers during a merge conflict because they didn't notice that a row was moved AND changed. As part of our pre-commit hook, the creation of the clone using SQL Data Compare with the /MakeScripts switch has the additional desirable side effect of creating all static data scripts with the insert statements ordered by the primary key of the table. Our pre-commit hook then replaces any static data creation script that was part of the original commit with the consistently ordered cloned version. This ensures all developers have the same order applied and makes it much easier to see how static data changed over time when viewing the git repository. The change in behavior prevents us from doing this anymore unless we stick with an older version or come up with a different method. An older version works for the short term but is not a viable solution. It would exclude us from bug fixes, new features, and security updates. My primary goal is to generate a version of the static data creation scripts in a consistent order. I could accomplish it by running two separate SQL Data Compare commands, one to create the schema scripts and one to copy the data. The issue that I have with that is that it forces us to do two completely separate SQL Data Compare operations. The inclusion of a single compare in our pre-commit hook already added a noticeable delay on every commit that involves static data. Adding a second compare operation would double the time it takes for the pre-commit hook to complete. It would be preferable to be able to run a single compare operation.. I don't have an issue using a different command, different switches, or even a completely different method - I'm mostly interested in accomplishing the same end result. I would even be satisfied with method that creates only the static data creation scripts. Please let me know if you have any suggestions. / comments

Thanks for confirming that there was a change in behavior.My specific use case is cloning the working version in a pre-commit hook on the SQL Source Control repository. Once the clone is made, the...

0 votes

Hi,Using V14.3.4.16598 or earlier, the /MakeScripts option creates a directory containing all object creation scripts including the static data in a data folder. Using version V14.4.0.16632 or late...

0 votes

CLI behavior change with /MakeScripts switch in 14.4

I'm using the Windows version of sqldatacompare.exe in a git pre-commit git hook script. An example of the command that it uses is:SQLDataCompare.exe /scripts1:d:\git\repo /MakeScripts:C:\temp\scri...

2 followers 5 comments 0 votes

How can we help you today?

rdaunce

Activity overview