Archive for the ‘v238’ Category

case(Capitalization) user defined identifier in SQL statement

Tuesday, October 4th, 2011

SQL Pretty Printer provides the ability to capitalize user defined identifier such as stored procedure name start with sp_ in SQL Server.

name: case_prefix_identitfer

setting path: capitalisation -> Prefix_ident

name: identifier_prefix_list

setting path: capitalisation -> Identifier prefix list

EXECUTE Sp_executesql
  @query,
  n’@age int’,
  @age = 25 

After setting case_prefix_identitfer to uppercase and identifier_prefix_list to sp_,

EXECUTE SP_EXECUTESQL
  @query,
  n’@age int’,
  @age = 25 

Upper case or lower case variable name in SQL statement

Tuesday, October 4th, 2011

Unlike some other SQL formatting tools, SQL Pretty Printer able to control the case of variable name in SQL statement, this feature helps you to find out variable in SQL statement quickly.

name: case_variable_name, default is no change.

setting path: capitalisation -> Variable

EXECUTE Sp_executesql
  @query,
  n’@age int’,
  @age = 25 

After setting case_variable_name to upper case,

EXECUTE Sp_executesql
  @QUERY,
  n’@age int’,
  @AGE = 25 

Upper case or lower case alias name in SQL statement

Tuesday, October 4th, 2011

Unlike some other SQL formatting tools, SQL Pretty Printer able to control the case of alias name in SQL statement, this feature helps you to find out alias in SQL statement quickly.

name: case_alias_name, default is no change.

setting path: capitalisation -> Alias

SELECT departmentname,
       Min(salary) AS min_salary
FROM   employees
GROUP  BY departmentname 

After setting case_alias_name to upper case,

SELECT departmentname,
       Min(salary) AS MIN_SALARY
FROM   employees
GROUP  BY departmentname 

Upper case or lower case column name in SQL statement

Tuesday, October 4th, 2011

Unlike some other SQL formatting tools, SQL Pretty Printer able to control the case of column name in SQL statement, this feature helps you to find out columns in SQL statement quickly.

name: case_column_name, default is no change.

setting path: capitalisation -> Column

SELECT department_id,
       Min(salary)
FROM   employees
GROUP  BY department_id 

After setting case_column_name to upper case,

SELECT DEPARTMENT_ID,
       Min(SALARY)
FROM   employees
GROUP  BY DEPARTMENT_ID 

Upper case or lower case table name in SQL statement

Tuesday, October 4th, 2011

Unlike some other SQL formatting tools, SQL Pretty Printer able to control the case of table name in SQL statement, this feature helps you to find out tables in SQL statement quickly.

name: case_table_name, default is no change.

setting path: capitalisation -> Table

SELECT department_id,
       Min(salary)
FROM   employees
GROUP  BY department_id 

After setting case_table_name to upper case,

SELECT department_id,
       Min(salary)
FROM   EMPLOYEES
GROUP  BY department_id 

sql formatter option: how to place a comma in the list of parameter in execute statement

Thursday, September 29th, 2011

This format option controls where to put comma in the list of parameters of SQL Server execute statement. a line break can be placed after comma, or before comma

name: exec_parameters_comma_option, default is put line break after comma

setting path: Execute -> parameter comma option

EXEC Spr_store_note
  @NoteId = 0,
  @TableTypeId = @TABLE_CUSTOMER,
  @RecordId = @CustomerId,
  @Descr = @Comments 

After set exec_parameters_comma_option to “before comma”, SQL will be formatted like this:

EXEC Spr_store_note
  @NoteId = 0
  ,@TableTypeId = @TABLE_CUSTOMER
  ,@RecordId = @CustomerId
  ,@Descr = @Comments 

After set exec_parameters_comma_option to “before comma with a space”, SQL will be formatted like this:

EXEC Spr_store_note
  @NoteId = 0
  , @TableTypeId = @TABLE_CUSTOMER
  , @RecordId = @CustomerId
  , @Descr = @Comments 

sql formatter option: list style of parameter in execute statement

Thursday, September 29th, 2011

This format option controls whether list style of parameters in SQL Server execute statement, it can be stacked or wrapped.

name: exec_parameters_style, default is stacked

setting path: Execute -> parameter style

EXEC Spr_store_note
  @NoteId = 0,
  @TableTypeId = @TABLE_CUSTOMER,
  @RecordId = @CustomerId,
  @Descr = @Comments 

After set exec_parameters_style to wrapped, SQL will be formatted like this:

EXEC Spr_store_note
  @NoteId = 0,@TableTypeId = @TABLE_CUSTOMER,@RecordId = @CustomerId,@Descr = @Comments 

sql formatter option: align value of parameter in execute statement

Thursday, September 29th, 2011

This format option controls whether align value of parameter of SQL Server execute statement.

name: exec_parameters_align_value, default is false

setting path: Execute -> align value of parameter

EXEC Spr_store_note @NoteId = 0,
                    @TableTypeId = @TABLE_CUSTOMER,
                    @RecordId = @CustomerId,
                    @Descr = @Comments 

After set exec_parameters_align_value to true, SQL will be formatted like this:

EXEC Spr_store_note @NoteId      = 0,
                    @TableTypeId = @TABLE_CUSTOMER,
                    @RecordId    = @CustomerId,
                    @Descr       = @Comments 

sql formatter option: first parameter of execute statement in new line

Wednesday, September 28th, 2011

This format option controls whether put a blank line before the first parameter of SQL Server execute statement.

name: exec_first_paramater_in_newline, default is true

setting path: Execute -> first parameter in newline

EXEC Spr_store_note
  @NoteId = 0,
  @TableTypeId = @TABLE_CUSTOMER,
  @RecordId = @CustomerId,
  @Descr = @Comments 

 

After set exec_first_paramater_in_newline to false, SQL will be formatted like this:

EXEC Spr_store_note @NoteId = 0,
                    @TableTypeId = @TABLE_CUSTOMER,
                    @RecordId = @CustomerId,
                    @Descr = @Comments 

SQL FORMATTER OPTION: SUBQUERY NEWLINE BEFORE COMPARISON OPERATOR

Tuesday, September 27th, 2011

This format option control whether put a blank line before comparison operator when it follows a subquery.

name: Subquery_Newline_Before_ComparisonOperator, default is false

setting path: subquery -> Linebreak before comparison operator

SELECT c.[Categoryid] AS [categoryid],
       c.[Categoryname],
       c.[Picture]
FROM   [northwind].[dbo].[CATEGORIES] c
WHERE  (((( (SELECT Sum([lpa_l1].[Unitsinstock]) AS [lpav_]
             FROM   (SELECT p.[Categoryid] AS [categoryid],
                            p.[Unitsonorder]
                     FROM   [northwind].[dbo].[PRODUCTS] p
                     WHERE  (( p.[Categoryid] = c.[Categoryid] ))) [lpa_l1]) > @p2 )))) 

After set Subquery_Newline_Before_ComparisonOperator to true, SQL will be formatted like this:

SELECT c.[Categoryid] AS [categoryid],
       c.[Categoryname],
       c.[Picture]
FROM   [northwind].[dbo].[CATEGORIES] c
WHERE  (((( (SELECT Sum([lpa_l1].[Unitsinstock]) AS [lpav_]
             FROM   (SELECT p.[Categoryid] AS [categoryid],
                            p.[Unitsonorder]
                     FROM   [northwind].[dbo].[PRODUCTS] p
                     WHERE  (( p.[Categoryid] = c.[Categoryid] ))) [lpa_l1])
             > @p2 ))))