How can we help you today? How can we help you today?
opc.three
Activity overview Badges (0) Posts (5) Comments (7)

Comments

Sort by recent activity
tanya wrote: Hello, Apologies for the inconvenience caused. Your suggestions are heard by Red Gate and the fix for this issue will be available in our next release scheduled for next week [image] I hope that helps. Thanks, Tanya Project Manager Red Gate Software Ltd Thank you for addressing this request in v4.0.1.2. / comments
  1. Community
  2. SQL Prompt 4 (Early Access Program)
  3. SQL Prompt and permissions
tanya wrote: Hello, Apologies for the inconvenience caused. Your suggestions are heard by Red Gate and the fix for this issue will be available in our next release scheduled for next week I hope...
0 votes
I am having the same issue. Can I make a suggestion red gate? Either make it so the escape button works to clear out these dialogs (less desirable) or have an option to not show exception dialogs at all and simply add them to an event log (most desirable). / comments
  1. Community
  2. SQL Prompt 4 (Early Access Program)
  3. SQL Prompt and permissions
I am having the same issue. Can I make a suggestion red gate? Either make it so the escape button works to clear out these dialogs (less desirable) or have an option to not show exception dialogs a...
0 votes
Indeed it was. I was on build 300. Build 315 has the fix. Thanks. / comments
  1. Community
  2. SQL Prompt
  3. BUG: incorrect alias attempt
Indeed it was. I was on build 300. Build 315 has the fix. Thanks.
0 votes
I cannot post the entire query however I did revisit this and see there is additional info when I hover over the red squiggly underline, it says: The column SomeID could not be resolved as a column with that name exists in multiple tables The use of the English language in the error message is dreadful however I made sure to type it in exactly as it is shown, i.e. that is the exact error message shown. By me adding a "target."-qualification to the column SomeID in my original code the error goes away however this should not be necessary because SQL Server does not require it, i.e. it is unambiguous so SQL Prompt should not complain. By definition "WHEN NOT MATCHED BY SOURCE" any additional predicates can only be referring to the target otherwise the predicate would be trivial. WHEN NOT MATCHED BY SOURCE AND SomeID = @SomeID THEN DELETE I have overcome the issue but I still think SQL Prompt should relax on this validation to match SQL Server. / comments
  1. Community
  2. SQL Prompt
  3. Error formatting MERGE statement in WHEN NOT MATCHED BY
I cannot post the entire query however I did revisit this and see there is additional info when I hover over the red squiggly underline, it says: The column SomeID could not be resolved as a colum...
0 votes
AndrewPierce wrote: SQL Prompt does not underline errors, that is done directly by SSMS' Intellisense. Hi again Andrew. I think the wires are getting crossed somehow. The underlining (or highlighting as SQL Prompt calls it) occurs after I attempt to format the code using SQL Prompt, e.g. pressing Ctrl+K, Ctrl+Y. The underline is a wavy red line and the error message is exactly: SQL Prompt was unable to complete this operation. Problem areas have been highlighted. To confirm, I have SSMS Intellisense disabled when this occurs. I hope this clarifies the issue. Hopefully this issue is not limited to my machine. If you would try formatting my repro code with my style settings using my version of SQL Prompt hopefully you can see what I see. / comments
  1. Community
  2. SQL Prompt
  3. Error when formatting otherwise valid SQL with subqueries
AndrewPierce wrote: SQL Prompt does not underline errors, that is done directly by SSMS' Intellisense. Hi again Andrew. I think the wires are getting crossed somehow. The underlining (or highli...
0 votes
Sorry, in my attempt to cleanse my actual code to provide repro code I neglected to take out the schema name. That said, the problem persists without the schema name. Please try it out with my version. USE tempdb; CREATE TABLE #tmp (id INT, name VARCHAR(100)) CREATE TABLE #tmp2 (id INT, name VARCHAR(100)) DELETE FROM #tmp WHERE id = ( SELECT id FROM #tmp2 WHERE name = 'abc' ) AND name = 'xyz'; My style document: <?xml version="1.0" encoding="utf-16" standalone="yes"?> <!----> <LayoutOptions version="1" type="LayoutOptions"> <ReservedWordsCasing>1</ReservedWordsCasing> <BuiltInFunctionCasing>1</BuiltInFunctionCasing> <BuiltInDataTypeCasing>1</BuiltInDataTypeCasing> <GlobalVariableCasing>0</GlobalVariableCasing> <DelimitIdentifiers>False</DelimitIdentifiers> <IndentationAmount>4</IndentationAmount> <TabIndentingBehaviour>0</TabIndentingBehaviour> <ReformatExpressions>True</ReformatExpressions> <FirstColumnOnNewLine>False</FirstColumnOnNewLine> <CommasAtStart>False</CommasAtStart> <MultilineSpacesAfterCommas>False</MultilineSpacesAfterCommas> <MultilineSpacesBeforeCommas>False</MultilineSpacesBeforeCommas> <MultilineAlignCommasWithStatement>True</MultilineAlignCommasWithStatement> <OperatorsOnNewline>True</OperatorsOnNewline> <OperatorsAtStart>True</OperatorsAtStart> <IndentBeginToken>False</IndentBeginToken> <IndentWithExpressionBrackets>True</IndentWithExpressionBrackets> <IndentWithParameterBrackets>True</IndentWithParameterBrackets> <IndentWithQueryBrackets>True</IndentWithQueryBrackets> <CloseBracketsOnNewLine>True</CloseBracketsOnNewLine> <OpenBracketsOnNewLine>True</OpenBracketsOnNewLine> <Wrap>False</Wrap> <WrapWidth>160</WrapWidth> <ShortLength>15</ShortLength> <CreateBracketsAtStartOfLines>True</CreateBracketsAtStartOfLines> <ParameterBracketOnNewline>True</ParameterBracketOnNewline> <CloseParameterBracketsOnNewLine>True</CloseParameterBracketsOnNewLine> <CompactShortStatements>False</CompactShortStatements> <SinglelineSpacesAfterCommas>True</SinglelineSpacesAfterCommas> <SinglelineSpacesBeforeCommas>False</SinglelineSpacesBeforeCommas> <SpacesAroundOperators>True</SpacesAroundOperators> <SpacesAroundComparisons>True</SpacesAroundComparisons> <FirstParameterDefinitionOnNewLine>True</FirstParameterDefinitionOnNewLine> <SpacesAfterBrackets>False</SpacesAfterBrackets> <LayoutSelectStatements>True</LayoutSelectStatements> <LayoutCreateStatements>True</LayoutCreateStatements> <QueryNewlineAfterOpenBracket>True</QueryNewlineAfterOpenBracket> <QueryNewlineBeforeCloseBracket>True</QueryNewlineBeforeCloseBracket> <JoinConditionsOnNewline>False</JoinConditionsOnNewline> <AlignConditionsWithJoins>False</AlignConditionsWithJoins> <AlignJoinsWithFrom>False</AlignJoinsWithFrom> <AlignSelectWithInsert>False</AlignSelectWithInsert> <IndentByKeywordWidth>False</IndentByKeywordWidth> <ColumnsOnSingleLine>False</ColumnsOnSingleLine> <DoNotIndentProcedureContents>True</DoNotIndentProcedureContents> <ExecuteParametersOnSingleLine>False</ExecuteParametersOnSingleLine> <IndentSelectSubclauses>False</IndentSelectSubclauses> <UseObjectDefinitionCase>True</UseObjectDefinitionCase> <CamelCaseNameOverrides /> <FormatActionLayout>True</FormatActionLayout> <FormatActionApplyCasing>True</FormatActionApplyCasing> <FormatActionInsertSemicolons>True</FormatActionInsertSemicolons> <FormatActionExpandWildCards>False</FormatActionExpandWildCards> <FormatActionQualifyObjectNames>True</FormatActionQualifyObjectNames> <FormatActionRemoveSquareBrackets>True</FormatActionRemoveSquareBrackets> </LayoutOptions> / comments
  1. Community
  2. SQL Prompt
  3. Error when formatting otherwise valid SQL with subqueries
Sorry, in my attempt to cleanse my actual code to provide repro code I neglected to take out the schema name. That said, the problem persists without the schema name. Please try it out with my vers...
0 votes
Anyone know the status of SC-2456 (mentioned by peter.peart in a 2012 post on this thread)? / comments
  1. Community
  2. SQL Compare Previous Versions
  3. Compare SQL Server Agent jobs
Anyone know the status of SC-2456 (mentioned by peter.peart in a 2012 post on this thread)?
0 votes
Total activity
17
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
5