Activity overview
Latest activity by drsql
That actually explains it quite well. I had always wondered why when things were clearly the exact same sometimes it suggested moving them.
Thanks,
Louis / comments
That actually explains it quite well. I had always wondered why when things were clearly the exact same sometimes it suggested moving them.
Thanks,
Louis
I guess what confuses me is that if I have two tables fred and bob, the UI doesnt say: Fred --> Bob
It says Fred -->
Bob (red)
So say I add: create index AnotherAbsolutelyDifferent on fred(fredId)
To my RedGateCompare2 database.. This time the result is: DefinitelyDifferent -> AbsolutelyDifferent
Same -> AnotherAbsolutelyDifferent
X Same
Now, same actually does match, so this seems to be a real bug, but the results I would have desired would be: Same Same
DefinitelyDifferent ->
X AbsolutelyDifferent
X AnotherAbsolutelyDifferent
Technically, the net effect is exactly the same, but it is completely clear what is taking place.
Now, if I could check only the subordinate items I want to ignore individually, that would be super too [image] (Should I make another post on that?) / comments
I guess what confuses me is that if I have two tables fred and bob, the UI doesnt say:Fred --> Bob
It saysFred -->
Bob (red)
So say I add:create index...
I see what you think I meant, but all I wanted was to have the totally different items on different lines so I could choose to add the new index and not drop the existing index. When they are on the same line with an arrow between them, it looks like the tool thought they were the same.
Just like if you have two tables with different names, you don't match them up, I would prefer that the two indexes be clearly denoted as distinct, different things so I could choose to keep both indexes. / comments
I see what you think I meant, but all I wanted was to have the totally different items on different lines so I could choose to add the new index and not drop the existing index. When they are on t...
matching things that are obviously not the same
Things that have no correlation to one another shouldn't have the ability to overwrite the item. For example, in the supplied script, there are indexes:
In one database:
create index DefinitelyDif...
FOR XML AUTO, TYPE
When I lay out:select *
from tableName
FOR XML AUTO, TYPE
I would expect that FOR XML AUTO, TYPE stay on one line with one spaces between the words. It actually is changed to:
select *
from...
First Line placement in Order By clause
When I lay out:SELECT ContactID, FirstName, LastName, Phone
FROM Person.Contact
ORDER BY ContactID
It does this:SELECT ContactID
, FirstName
, LastName
...
Subquery placement
Not to be overly picky, but on the Subquery placement option you have the following code:SELECT *
FROM ( SELECT staffId
FROM personnel )
CROSS JOIN (...
On further review, it seems to be a bug with the option:
General, Commas, Multiple Line Statements
The two "Space after comma" settings. When they are not checked, there will be no space between the As and the first value. For example: select 'hi' as fred,
'bye' as barney
from test
is layed out as: select 'hi' as fred
, 'bye'as barney
from test
Apparenly it is removing the space from the wrong location. So the workaround is to turn on the Space after comma. Not a big deal, but it looks funny : select 'hi' as fred
, 'bye' as barney
from test
/ comments
On further review, it seems to be a bug with the option:
General, Commas, Multiple Line Statements
The two "Space after comma" settings. When they are not checked, there will be no space between t...
Problem with case expression in SELECT clause
When I use Lay Out SQL onselect value, case
when datediff(yyyy, p.TransactionDate, getdate()) = 0 then sum(p.Amount)
...
Quoted Identifiers
When I format:
SELECT *
FROM bob --a table I have created
It expands to:SELECT [bob].[bobId], [bob].[value]
FROM bob --a table I have created
With the ...