Activity overview
Latest activity by DavidHerbst
Thanks for your response Jason and I understand that you there may be difficulties that prevent this from being implemented in the near future.
What I don't understand is how the authentication and security issues would be different than the ones you've already solved for the "Cross database queries" support you added in the 3.5 release.
Synonyms are just aliases, authentication and security is still based on the underlying object they are pointing at. See code example below.
Am I missing something here?
E.g.
USE OtherDb
CREATE SYNONYM dbo.CreditCard FOR AdventureWorks.Sales.CreditCard
-- Either both of the following queries will fail or both of them will succeed based on authentication and security settings.
SELECT *
FROM CreditCard
SELECT *
FROM AdventureWorks.Sales.CreditCard
/ comments
Thanks for your response Jason and I understand that you there may be difficulties that prevent this from being implemented in the near future.
What I don't understand is how the authentication and...
Thanks Jason! / comments
Thanks Jason!
I hear what you are saying about too many icons being confusing. On the other hand foreign key columns frequently have the same name in both tables so at a quick glance they wouldn't be distinguished from candidates based only on the column names. E.g. Customer.CustomerID and CustomerAddress.CustomerID.
Possibly you could use the same paper clip image but a different overlay for each icon variation.
E.g.
1) A paper clip overlaid with a key for candidates based on a foreign key.
2) A paper clip overlaid with "N" for candidates based on matching column names.
3) A paper clip overlaid with "T" for candidates based on matching data types. / comments
I hear what you are saying about too many icons being confusing. On the other hand foreign key columns frequently have the same name in both tables so at a quick glance they wouldn't be distinguis...
Less prompting of autocomplete candidate lists
Can the prompting of autocomplete candidate lists be more discriminating or less aggressive like it was in 2.0? Or can this be made configurable?
E.g. in 3.5 when typing "FROM Person.ContactType ...
Use 2.0 style parameter help/hints for system Functions?
Can you put back the 2.0 style parameter help/hints for system Functions? E.g. in 2.0 the autocomplete text inserted for the DATEPART is "DATEPART(datepart, date)" but in 3.5 it is only "DATEPART(...
Different special icon for foreign key rel Join Conditions
I have additional matches enabled for "Column names" and "Data types" for cases where I am joining tables that do not have a foreign key relationship explicitly defined.
However when I am joining t...
Special icon for Foreign Key relationship JOIN candidates
First of all, thank you so much for adding Foreign Key relationship JOIN candidates to the top of the JOIN candidate list in the 3.5 release!
Now would it be possible for you to enhance SQL Promp...
SQL Server 2005 Synonyms not supported in 3.5?
I just upgraded to 3.5 but my table Synonyms are not showing up in the autocomplete candidate lists after the FROM or JOIN keywords are typed.
In addition, typing table Synonyms does not bring up a...