How can we help you today? How can we help you today?
Bernard Sheppard
Fair enough for the WMI access. However, ideally, I'd like two default accounts - one for WMI, and one for SQL - it allows finer grained control over the rights assigned to each account. I guess it is too late given this is an RC. / comments
Fair enough for the WMI access. However, ideally, I'd like two default accounts - one for WMI, and one for SQL - it allows finer grained control over the rights assigned to each account. I guess i...
0 votes
RogueDog wrote: ...So my suggestion is to give SQL Prompt the ability to recognize when aliases are being used and then if they are being used to require them prior to each field. I think this is a style issue, and I disagree with it. SQL Prompt recognises aliases (e.g. x.), and prompts for field names for the given alias on join or where clauses - which is what I expect. I don't want to be forced to use aliases for every column, only for those that are ambiguous. Here's what I tend to do, and why I prefer this idea... I tend to start a complex query with top 10 * as my select list, while I then set up the from clause with it's joins. I use aliases there, and then in the where clause as I refine it. Given that I have the aliases defined by the time I type my where clause, SQL Prompt is all good at that point, with good intellisense prompting. I find that having all fields from all tables visible initially helps me visualise the data that I'm retreiving, and helps me spot where my join or restriction criteria aren't quite right. I then create my select list once I'm happy with the rest of the query, and at that point have a pretty good idea of which columns need to be disambiguated (because I've already used them to join). I tend not to use aliases for other columns - both because their owning table is self evident, but also because I want SQL Server to let me know if I've got an ambiguous column - because that indicates to me that I don't yet fully understand the underlying tables and views in a query I'm writing. In other words, if I get a warning that a given column is ambiguous (and I didn't expect it), it makes me review a given query. Perhaps I'm joining a table that I don't require (because it is already joined inside a view that I'm using). Perhaps I've not specified my join criteria correctly (and so I haven't actually specified a true inner join). If SQL Prompt forced me to always qualified aliased tables, then I'd never get the chance to see ambiguous columns. The fact that I do alerts me to the possibility that I haven't written an optimal query. / comments
RogueDog wrote: ...So my suggestion is to give SQL Prompt the ability to recognize when aliases are being used and then if they are being used to require them prior to each field. I think this...
0 votes