184 results found

1. Trim white space

   Please add an option be added to SQL Prompt to trim all white space.

   Ideally, the following would be supported:
   - Ability to execute against a query window or block of selected code
   - Available as a stand-alone shortcut
   - Can include as part of a Format SQL style
   - Option to remove a) leading spaces, b) trailing spaces, c) both

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Format SQL  ·  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

2. Automatically create variables for use with generating full INSERT statements

   Currently the behavior for inserting a full INSERT statement is that it produces something like this:

   INSERT INTO dbo.ContactPictures
   ( InterActionPersonalContactID ,
   InterActionFirmContactID ,
   ImageFileStoreFilePathSegment ,
   Source ,
   ManuallyCreatedByUserAccountName ,
   DateTimeLastUpdated
   )
   VALUES ( 0 , -- InterActionPersonalContactID - int
   0 , -- InterActionFirmContactID - int
   '' , -- ImageFileStoreFilePathSegment - varchar(256)
   '' , -- Source - varchar(20)
   N'' , -- ManuallyCreatedByUserAccountName - nvarchar(40)
   GETDATE() -- DateTimeLastUpdated - datetime
   )

   Hard-coded values are rarely what's needed, though; it would be very useful if it could generate variables and use them in the statement, like this:

   DECLARE @InterActionPersonalContactID INT = 0 ,
   @InterActionFirmContactID INT = 0 ,
   @ImageFileStoreFilePathSegment NVARCHAR(256) = '' ,
   @Source VARCHAR(20) = '' ,
   @ManuallyCreatedByUserAccountName NVARCHAR(40) = N'',
   @DateTimeLastUpdated DATETIME = GETDATE()

   INSERT INTO dbo.ContactPictures
   ( InterActionPersonalContactID ,
   InterActionFirmContactID ,
   ImageFileStoreFilePathSegment ,
   Source ,
   ManuallyCreatedByUserAccountName ,
   DateTimeLastUpdated
   )
   VALUES ( @InterActionPersonalContactID ,
   @InterActionFirmContactID ,
   @ImageFileStoreFilePathSegment ,
   @Source ,
   @ManuallyCreatedByUserAccountName ,
   @DateTimeLastUpdated
   
   )

   Currently the behavior for inserting a full INSERT statement is that it produces something like this:

   INSERT INTO dbo.ContactPictures
   ( InterActionPersonalContactID ,
   InterActionFirmContactID ,
   ImageFileStoreFilePathSegment ,
   Source ,
   ManuallyCreatedByUserAccountName ,
   DateTimeLastUpdated
   )
   VALUES ( 0 , -- InterActionPersonalContactID - int
   0 , -- InterActionFirmContactID - int
   '' , -- ImageFileStoreFilePathSegment - varchar(256)
   '' , -- Source - varchar(20)
   N'' , -- ManuallyCreatedByUserAccountName - nvarchar(40)
   GETDATE() -- DateTimeLastUpdated - datetime
   )

   Hard-coded values are rarely what's needed, though; it would be very useful if it could generate variables and use them in the statement, like this:

   DECLARE @InterActionPersonalContactID INT = 0… more

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Format SQL  ·  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

3. Template based formatting with different

   Template based formatting.
   Select your text and right click, format according to template... then select the appropriate template of your choice.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  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

4. Switch between Alias formats AS/=

   A formatting feature to change syntax between these two forms

   SELECT field1 AS Alias1, field2 AS Alias2 FROM table1

   SELECT Alias1 = field1, Alias2 = field2 FROM table1

   Ideally useable without having to invoke the "Format SQL" command.
   Hopefully selectable as an enabled option within a Format SQL style set.

   I spend a non-trivial amount of time reformatting SQL code for leading/trailing comma placement and alias AS/= placement, this would be a HUGE help

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  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

5. Formatting option to columnize not only column names but data-types and nullability as well

   Some of us would like the option for formatting of table declarations to not only align [tabify] column names (indented one tab), but also columnize/tabify the data types and nullability so that table definitions are grid-like. Constraints per column are are far more variable and therefore require more of a free format or sometimes pushing them to subsequent lines, but at minimum, the ColumnName, DataType and Nullability should be optioned to columnize by default.

   When there are hundreds or thousands of tables in a db schema, I'm used to scanning table definitions, and having them organized grid-like saves my eyeballs time and frustration. I realize not everyone organizes table schema in this way, but I manually format every table definition this way where I am allowed.

   Some of us would like the option for formatting of table declarations to not only align [tabify] column names (indented one tab), but also columnize/tabify the data types and nullability so that table definitions are grid-like. Constraints per column are are far more variable and therefore require more of a free format or sometimes pushing them to subsequent lines, but at minimum, the ColumnName, DataType and Nullability should be optioned to columnize by default.

   When there are hundreds or thousands of tables in a db schema, I'm used to scanning table definitions, and having them organized grid-like saves my eyeballs… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Format SQL  ·  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

6. Formatting Styles - More granular control?

   I realize my title is very vague.

   Basically, I would like more control options over how styles are applied. Maybe I'm just really weird in how I format my SQL, but it seems like no matter how hard I try, I can never get the styles the way I want them.

   I realize that it's impossible to make it perfect. But the basic idea is to get the formatter to do what you would normally do the majority of the time.

   For example....the majority of the time, I prefer the following...

   For JOIN clauses, all join criteria is in the same line:

   JOIN dbo.Table t ON t.Foo = x.Foo AND t.Bar = x.Bar
   

   But for WHERE clauses, I prefer them to be on separate lines:
   WHERE x.Foo = 1
   AND x.Bar = 2
   AND y.Baz = 123

   Unfortunately, the formatter only allows one or the other.

   Another example, is with lists:
   For GROUP BY, I like them all on the same line

   GROUP BY x.Foo, y.Bar, z.Baz
   

   But for SELECT, I like the columns on separate lines (unless it's a short list, then put them all on the same line.)

   Unfortunately, the formatter also does not allow this. So now all of my group by's look like this:

   GROUP BY x.Foo
       , y.Bar
       , z.Baz
   

   I have a few more examples, but they're more oddball things that I like to do that are probably not as common.

   I realize my title is very vague.

   Basically, I would like more control options over how styles are applied. Maybe I'm just really weird in how I format my SQL, but it seems like no matter how hard I try, I can never get the styles the way I want them.

   I realize that it's impossible to make it perfect. But the basic idea is to get the formatter to do what you would normally do the majority of the time.

   For example....the majority of the time, I prefer the following...

   For JOIN clauses, all join criteria is in the… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Format SQL  ·  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

7. align aliases

   Please, separate options to align aliases for columns and tables..... I love aligned column aliases, but table aliases advance too far right, unnecessarily.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Format SQL  ·  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

8. More Casing/Capitalization Options

   Regardless of the source table, we would like the option to force table, column, and alias names to lower case. (We integrate databases from multiple sources and our queries look like a mess when half of the columns are upper case and half are lower).

   Example:
   SELECT dp.PROJID AS cpprojid,
   pld.suffix AS projectsegment,
   IP.projectnumber AS innprojid
   FROM DEL.PROJ AS dp
   INNER JOIN DEL.viewprojectlvldetail AS pld
   ON pld.PROJID = dp.projid
   LEFT OUTER JOIN inn.PROJ AS IP
   ON dp.PROJID LIKE IP.cpproj_id + '%'

   I think this is hard to read. We'd prefer the keywords to standout as uppercase and standardize all out table/column/alias names as lower case so they're easier to read and all of our servers/databases are of a Collation that can support it.
   
   Preferred format:

   SELECT dp.projid AS cpprojid,
   pld.suffix AS projectsegment,
   ip.projectnumber AS innprojid
   FROM del.proj AS dp
   INNER JOIN del.viewprojectlvldetail AS pld
   ON pld.projid = dp.projid
   LEFT OUTER JOIN inn.proj AS ip
   ON dp.projid LIKE ip.cpproj_id + '%'

   Regardless of the source table, we would like the option to force table, column, and alias names to lower case. (We integrate databases from multiple sources and our queries look like a mess when half of the columns are upper case and half are lower).

   Example:
   SELECT dp.PROJID AS cpprojid,
   pld.suffix AS projectsegment,
   IP.projectnumber AS innprojid
   FROM DEL.PROJ AS dp
   INNER JOIN DEL.viewprojectlvldetail AS pld
   ON pld.PROJID = dp.projid
   LEFT OUTER JOIN inn.PROJ AS IP
   ON dp.PROJID LIKE IP.cpproj_id + '%'

   I think this is hard… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  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

9. Allow LEFT, RIGHT, INNER and OUTER JOINS to be right-aligned to SELECT.

   Currently, FROM, WHERE, JOIN, and ODER can all be right-aligned to SELECT when formatting SQL. However, if you introduce a LEFT JOIN, the LEFT keyword is right-aligned to SELECT, and everything else is pushed over to make room for the JOIN. This is hideous and makes no sense.

   Instead, allow the entirety of "LEFT JOIN", "RIGHT JOIN", "INNER JOIN" and "OUTER JOIN" to right-align to the SELECT keyword.

   The attached images explain it better than I can.

   •  

   •  

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  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

10. Enable block comments in SQL

    SQL Prompt and SSMS do not have the option to create/remove block comments. This is a serious problem.

    We SQL Prompt users would love the option to add/remove block comments in SQL, between the marks /* and */, because they sometimes serve very different purposes.

    Inline comment options (Ctrl + K, Ctrl + C or Ctrl + K, Ctrl + U) are helpful, but they don't always do exactly what we need. Sometimes they can break things. See below.

    /*
    Sometimes we need block comments that cover multiple lines.
    Like this.
    /
    / Or comments where each line begins and ends with the markers. /
    / Like this. */

    Sometimes inline comments, beginning with "- -", get inadvertently uncommented, and it can have major consequences. For one, it can be VERY hard to find the old textual comments. More importantly, lines of SQL code get uncommented, and they can alter or delete an entire table's contents.

    -- A line of test code might feature a truncation from an earlier version
    -- truncate table_name;

    Can you please add a button/hot key combination that will add/remove comments that begin with /* and end with */?

    NOTE:
    This feature is available in other IDEs like Visual Studio and VS Code:
    - Windows: Shift + Alt + A
    - Mac: Shift + Option + A

    SQL Prompt and SSMS do not have the option to create/remove block comments. This is a serious problem.

    We SQL Prompt users would love the option to add/remove block comments in SQL, between the marks /* and */, because they sometimes serve very different purposes.

    Inline comment options (Ctrl + K, Ctrl + C or Ctrl + K, Ctrl + U) are helpful, but they don't always do exactly what we need. Sometimes they can break things. See below.

    /*
    Sometimes we need block comments that cover multiple lines.
    Like this.
    /
    / Or comments where each line begins and… more

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Format SQL  ·  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

11. Add the ability to specify a named formatting style using a comment block.

    Add the ability to specify a named formatting style using a comment block.

    Add functionality to specify, in a comment block, what formatting style should be used when formatting the current file. It could be a simple addition to the existing turn-on/off formatting comment.

    Perhaps something like this:
    --SQL Prompt Formatting On - Style = "My Style"

    The above would turn on formatting and specify what style to use.

    This functionality would be helpful in many ways.

    • It is already convenient to have multiple formatting rules, this would keep the user from having to remember what rules apply to what file

    • When formatting a group of files from the command line, the files themselves could specify their own formatting rules, in case one needs different formatting for different files.

    • It would also be convenient to be able to have different blocks of code in the same file obey different styles (condensed for one section and a wide,long-line one) for different sections of code. This has to be done using manual formatting using the existing on/off comments.

    Add the ability to specify a named formatting style using a comment block.

    Add functionality to specify, in a comment block, what formatting style should be used when formatting the current file. It could be a simple addition to the existing turn-on/off formatting comment.

    Perhaps something like this:
    --SQL Prompt Formatting On - Style = "My Style"

    The above would turn on formatting and specify what style to use.

    This functionality would be helpful in many ways.

    • It is already convenient to have multiple formatting rules, this would keep the user from having to remember what rules apply to what… more

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  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

12. Add or remove square brackets (easily!)

    Have buttons to add/remove square brackets rather than tucked away under Options, so they can be toggled on or off easily.

    And/or move the square brackets option out of Options and into the actual formatting style (like the option to remove additional whitespace) so it can be saved and shared as a template

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  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

13. Option to prevent removal of brackets on database and server names

    Removing brackets from database names causes VS schema compare to indicate file differences because VS requires database reference variables to be enclosed in brackets. Need an option to exclude removal of brackets from database and server in three and four part names.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  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

14. Unformat Query

    Add a menu Item option to unformat a query. In other words take the query that is highlighted or every query in the script and convert them to be on a single line with only a single space between keywords, words, and operators.
    This would be very useful for having to copy SQL into a table or other some object that shouldn't have normal formatting in it.
    An option would be to double up all single quotes, so that the query can be placed between single quotes.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  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

15. Properly format the start of a CTAS in Azure Synapse Analytics

    SQL Prompt does not start a new line for the SELECT portion of a CTAS statement within Azure Synapse Analytics when there is a defined distribution or index using a WITH clause. Instead the SELECT statement is tabbed way over to the right.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  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

16. Auto-generate MERGE comparison clauses

    One of the most tedious elements of writing T-SQL is handling of proper comparisons in the WHEN MATCHED AND ... THEN UPDATE clause of a MERGE statement.
    For example, to compare a single nullable target and destination column you should compare:

    SRC.column <> TGT.column
    OR (SRC.column IS NULL AND TGT.column IS NOT NULL)
    OR (SRC.column IS NOT NULL AND TGT.column IS NULL)

    I'm not sure on exactly how would be best to handle this but it would be great if SQL Prompt could somehow auto-populate these clauses. Or even better would be some way to generate an entire merge statement for two similar tables. When merging tables with many columns, this would be a huge time-saver. Additionally, these comparisons are highly susceptible to user-error do to the repetitive nature of the task.

    One of the most tedious elements of writing T-SQL is handling of proper comparisons in the WHEN MATCHED AND ... THEN UPDATE clause of a MERGE statement.
    For example, to compare a single nullable target and destination column you should compare:

    SRC.column <> TGT.column
    OR (SRC.column IS NULL AND TGT.column IS NOT NULL)
    OR (SRC.column IS NOT NULL AND TGT.column IS NULL)

    I'm not sure on exactly how would be best to handle this but it would be great if SQL Prompt could somehow auto-populate these clauses. Or even better would be some way to generate an entire merge statement… more

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  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

17. Automatically add Schema to tables when formatting.

    Provide the option to enable automatic schema addition when necessary. And when there may be more than one candidate schema, provide a warning

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  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

18. Outlining

    Would be great to be able to add user specific outlining, so that you could add + & - where ever you choose in a sql script to collapse down certain parts. The CRM system that I support has a create contact table import with 200 columns which is regularly used and this functionality would be great when having to resort to using this import etc...

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  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

19. New Case When Intend option

    The new option would allow intending from alias (in alias = expression notation)

    •  

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  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

20. Copy as IN clause should follow formating setting

    I use the Copy as IN clause a lot and think it is one of the most helpful functions in SQL Prompt.

    It would be even better if it could format the IN list according to the Style setting you have selected.

    This is how it is created when right clicking on the function
    ContractsId IN
    (
    234151,
    234321,
    239990,
    228809,
    240808,
    231809,
    240021,
    230876,
    231739,
    239555,
    240972
    )

    If I then use format SQL it changes it to the way I want it, without line brakes for each row but in relation to the other statement.

    It would be nice if the formating of the right click function followed the Style setting for IN lists.

    SELECT *
    FROM tra.ContractDetailView
    WHERE SourceSystemNo = 4
    AND ContractsId IN (234151, 234321, 239990, 228809, 240808, 231809, 240021, 230876, 231739, 239555, 240972)

    I use the Copy as IN clause a lot and think it is one of the most helpful functions in SQL Prompt.

    It would be even better if it could format the IN list according to the Style setting you have selected.

    This is how it is created when right clicking on the function
    ContractsId IN
    (
    234151,
    234321,
    239990,
    228809,
    240808,
    231809,
    240021,
    230876,
    231739,
    239555,
    240972
    )

    If I then use format SQL it changes it to the way I want it, without line brakes for each row but in relation to the other statement.

    It would be… more

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  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