How can we help you today? How can we help you today?
Bernard Sheppard
Activity overview Badges (0) Posts (12) Comments (21)

Comments

Sort by recent activity
I've received the other updates, but not this one. Is it possible the mailing list didn't send properly, or for all recipients? / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. SQL Prompt 5 final early access release
I've received the other updates, but not this one. Is it possible the mailing list didn't send properly, or for all recipients?
0 votes
Hi Luke, Both the failed initial install, and the automatic Windows 7 prompted retry were from the same download. Cheers B. / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. Final Early Access (5.0.0.591) Install Fails
Hi Luke, Both the failed initial install, and the automatic Windows 7 prompted retry were from the same download. Cheers B.
0 votes
I miss my SQL Refactor keystrokes - annoying I have to learn new ones to Format SQL rather than to Layout SQL. Minor niggle, but would be a good option to allow "SQL Refactor shortcut keys". / comments
  1. Community
  2. SQL Prompt 5 EAP
  3. Uninstall SQL Refactor before installing SQL Prompt 5
I miss my SQL Refactor keystrokes - annoying I have to learn new ones to Format SQL rather than to Layout SQL. Minor niggle, but would be a good option to allow "SQL Refactor shortcut keys".
0 votes
I tried upgrading (The PC was upgraded from Vista to Win7). I then uninstalled all of the Red Gate programs, and kicked off a new install. Toolbelt was run as a user in the Administrator group, by right clicking, and choosing run as Administrator. / comments
  1. Community
  2. SQL Doc Previous Versions
  3. Installer Fail on Windows 7 x64 (Ultimate, RTM)
I tried upgrading (The PC was upgraded from Vista to Win7). I then uninstalled all of the Red Gate programs, and kicked off a new install. Toolbelt was run as a user in the Administrator group, by ...
0 votes
I tried upgrading (The PC was upgraded from Vista to Win7). I then uninstalled all of the Red Gate programs, and kicked off a new install. Toolbelt was run as a user in the Administrator group, by right clicking, and choosing run as Administrator. / comments
  1. Community
  2. SQL Dependency Tracker
  3. Installer Fail on Windows 7 x64 (Ultimate, RTM)
I tried upgrading (The PC was upgraded from Vista to Win7). I then uninstalled all of the Red Gate programs, and kicked off a new install. Toolbelt was run as a user in the Administrator group, by ...
0 votes
Agreed. Replication in some scenarios (e.g. web replication over firewalls) can be really hard to get working. Although you can then script out a working replication set up, and edit the scripts to get it running on another set of servers, having the settings documented would be brilliant - and useful as well simply to avoid the need to script out replication objects to see how they are set up, or dive through layers of properties dialogs. / comments
  1. Community
  2. SQL Doc Previous Versions
  3. please please please
Agreed. Replication in some scenarios (e.g. web replication over firewalls) can be really hard to get working. Although you can then script out a working replication set up, and edit the scripts t...
0 votes
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
  1. Community
  2. SQL Response v1 RC
  3. Problems installing on a DC
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
Can you establish a VPN to the servers and connect over the VPN (thus getting access to 1433 as well as 135, without exposing it to the internet)? / comments
  1. Community
  2. SQL Response v1 RC
  3. WMI Error: The object exporter specified was not found
Can you establish a VPN to the servers and connect over the VPN (thus getting access to 1433 as well as 135, without exposing it to the internet)?
0 votes
I noticed the same sort of problem: in master db, when I type select * from mydb. SQL Prompt shows it's balloon tip with the message retrieving data for database mydb If I then choose myDB from the QA DB Combo box, and type select * from SQL Prompt shows it's balloon tip with the message retrieving data for database myDB It's already got that metadata, of course! / comments
  1. Community
  2. SQL Prompt 2
  3. Table name is case sensitive for JOIN ... ON trigger
I noticed the same sort of problem: in master db, when I type select * from mydb. SQL Prompt shows it's balloon tip with the message retrieving data for database mydb If I then choose myDB fr...
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
  1. Community
  2. SQL Prompt 2
  3. Alias Unfriendly
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
Total activity
52
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
19