9 results found

1. Analyze code in order even with GOTO; Showing code issues with GOTO code now

   When using GOTO statement, code that should be reviewed inside the GOTO statement is showing with issues underlined. "The multi-part identifier 'ep_view.MemberNumber' could not be bound".

   Would be nice if the code was analyzed as it would be executed so these errors are not present. Takes away from the effectiveness of using SQL Complete.

   While I don't use GOTO as a habit, this is a large VIEW that runs faster inside so a GOTO to the code at the end works well. Then a simple command can load it only on the initial run and save time for following TESTING since it is already loaded in the temp file.

   IF OBJECTID('tempdb..#tmpExchangePremiumEffDateView') IS NULL
   GOTO ExchangePremiumEffDateView

   When using GOTO statement, code that should be reviewed inside the GOTO statement is showing with issues underlined. "The multi-part identifier 'ep_view.MemberNumber' could not be bound".

   Would be nice if the code was analyzed as it would be executed so these errors are not present. Takes away from the effectiveness of using SQL Complete.

   While I don't use GOTO as a habit, this is a large VIEW that runs faster inside so a GOTO to the code at the end works well. Then a simple command can load it only on the initial run and save time for following TESTING… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Collation names enclosed in square brackets is invalid

   I have "Enclose identifiers within square bracket" set to "Always", which in most cases are great.
   However, collation names are also being enclosed in square brackets, which seems to be invalid.
   Please correct.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminPMs (Admin, Devart) responded

   Could you please specify what product version you are using?

   A video or screenshots would be also of help.

3. SQL Complete does not support parsing SQL with valid PATINDEX function

   SQL Complete does not support parsing SQL with valid PATINDEX function

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminDevart (_, Devart) responded

   Could you please provide us the specific example of this?

4. Remove debug stamp in Releases (keep it for your Debug versions only or verbose mode)

   Steps to reproduce:
   - run app DebugView
   - work with SQL Complete for sometime in SSMS
   - keep watching DebugView until you'll see lots of debug messages generated by SQLComplete

   Expected: no debug messages in Release binaries
   Actual: there are debug messages

   Please chekc all other products for this.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminDevart (_, Devart) responded

   We will fix it in one of the next product builds.

5. Allow the 'on' clause to be aligned with the JOIN clause

   "Support" was of no assistance, but I'd like to have my 'On' clause aligned with the join clause, but it's not possible:

   from
   [ExtendedEvents].[Events] ee -- on new line
   join
   OtherTable
   on -- inline with JOIN
   OtherTable.[ID] = ee.[ID]
   
   where

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminDevart (_, Devart) responded

   This can be setup as follows:
   1. Select ‘SQL Complete → Options…’ from the main menu. The ‘Options’ window opens.
   2. Navigate to the ‘Formatting → Profiles’ branch.
   3. Select the active profile and click the ‘Open Selected…’ button.
   4. Navigate to the ‘SELECT → FROM → JOIN’s’ section.
   5. Unselect the ‘Indent ON keyword by 4 columns’ option.

6. In 'where' clause align the conditions to allow easier column selection

   "Support" were or no assistance. I'd like to align the where clause so that I can column select the conditions, bu aligning the logical operators with the where clause:

   where
   [collectionid] > 5396 -- alignment
   and [sessionid] = 114 -- alignment

   currently the code gets formatted as:
   where
   [collectionid] > 5396 -- alignment
   and [sessionid] = 114 -- alignment

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminPMs (Admin, Devart) responded

   Could you please provide us screenshots of the actual and expected results along with the script?

7. code completion not working when db is offline

   when db is offline during ssms startup - it won't get code completion.
   you have to bring it online and restart ssms

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminDevart (_, Devart) responded

   Could you please clarify if it does not work only for offline databases or for each database on the server?

   A video or screenshots would be also of help.

8. Refactoring suggestions

   I really love the refactoring features, but came across 2 things that might be addressed.

   1. when renaming procedure variable and the same variable name is used in other SP that is called using explicit variable assignment, e.g.
      EXEC dbo.otherSp @variable = @variable,
      the other SP variable gets renamed as well
      (e.g. rename
      @variable to @newName creates
      EXEC dbo.otherSp @newName = @newName
      instead of
      EXEC dbo.otherSp @variable = @newName)
      when variable is part of an EXEC command and parameter contains assignment operator, only the variable following an assignment operator should be renamed

   2. when leaving table alias as it is and changing the source table for the alias
      if the new table does not contain column names used throughout the procedure,
      inexistent column names get underlined as expected in most cases (selects, joins on...) but not for ROW_NUMBER() OVER (PARTITION BY /ORDER BY) inside OVER block, it seems like it's a valid column name
      if renaming the alias works inside this blocks, so should the intellisense when changing the source of an alias in all places the alias is used

   otherwise it's great feature and thank You for it, really helps ;)

   I really love the refactoring features, but came across 2 things that might be addressed.

   1. when renaming procedure variable and the same variable name is used in other SP that is called using explicit variable assignment, e.g.
      EXEC dbo.otherSp @variable = @variable,
      the other SP variable gets renamed as well
      (e.g. rename
      @variable to @newName creates
      EXEC dbo.otherSp @newName = @newName
      instead of
      EXEC dbo.otherSp @variable = @newName)
      when variable is part of an EXEC command and parameter contains assignment operator, only the variable following an assignment operator should be renamed

   2. when leaving table alias as it is and changing… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. F12

   По F12 объект ищется в текущей базе. Но поиск не срабатывает и падает с ошибкой если:

   1. В базе стоит фильтр, и обьект не может быть найден при текущем фильтре.
   2. Если в окне студии открыт например код процедуры - и он трактуется как некорректный, например из за того что процедура уже есть в базе, а открытый скрипт начинается с CREATE PROCEDURE... То по F12 также выпадет ошибка. Нужно вручную заменить CREATE например на ALTER, только в этом случае поиск по F12 опять сработает.

   Более того, вцелом неудобно сначала по F12 делать поиск, а потом дополнительно на найденом объекте по выпадающему меню выбирать - "открыть скрипт в новом окне". В конкурирующих разработках, даже в самых дешевых - есть возможность сразу показать скрипт создания объекта. Было бы намного удобнее просто на любом объекте - иметь возможность сразу посмотреть скрипт создания. Жду эту дороботку уже который год...

   По F12 объект ищется в текущей базе. Но поиск не срабатывает и падает с ошибкой если:

   1. В базе стоит фильтр, и обьект не может быть найден при текущем фильтре.
   2. Если в окне студии открыт например код процедуры - и он трактуется как некорректный, например из за того что процедура уже есть в базе, а открытый скрипт начинается с CREATE PROCEDURE... То по F12 также выпадет ошибка. Нужно вручную заменить CREATE например на ALTER, только в этом случае поиск по F12 опять сработает.

   Более того, вцелом неудобно сначала по F12 делать поиск, а потом дополнительно на найденом объекте по выпадающему меню… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating