User profile for Bernard Sheppard

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

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

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

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

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

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

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

My issue is that my client (who would be purchasing the tool) would not look at it as $57 per developer for three developers and $57 per DBA for two DBAs, they'd unfortunately look at it as $95 per developer for 40 developers (37 who only use Oracle), and $95 per DBA for 6 DBAs (4 who only look at Oracle). They manage to get the concept of an enterprise agreement with Microsoft, but not appropriate price breaks for dev tools - for some bizarre reason they insist on costing dev tools on a per person basis. / comments

My issue is that my client (who would be purchasing the tool) would not look at it as $57 per developer for three developers and $57 per DBA for two DBAs, they'd unfortunately look at it as $95 per...

0 votes

Following on from the scroll to candidate list rather than filter suggestion elsewhere, a more context sensitive candidate list would be good. For example, if I include functions & system functions in the options, they naturally sort to the top of the list - but most of the time I'm actually interested in columns - particularly columns on tables already referred to in my query. As a result, columns for tables already included in a query should filter to the top of the list - making the list a more useful reminder when you don't know the name of the column you're interested in - so you want to select from a list. So, if I have all (or most) options selected in the Items to show in candidate list, and my query so far is select * from aardvarks a join zebras z on a.id = z.id where@CONNECTIONS. If I actually do want to use a system function, then typing @ will bring it into focus. / comments

Following on from the scroll to candidate list rather than filter suggestion elsewhere, a more context sensitive candidate list would be good. For example, if I include functions & system functions...

0 votes

I'd second this - even though I didn't use the original tool. The loss of the ability to open a pre-defined V3/V4 project for SQL Compare and Data Compare means I'm still using V4 instead of V5 - I haven't been bothered to run both side by side and re-setup my comparison projects in V5. / comments

I'd second this - even though I didn't use the original tool. The loss of the ability to open a pre-defined V3/V4 project for SQL Compare and Data Compare means I'm still using V4 instead of V5 - I...

0 votes

SQL Backup log file 26/04/2006 10:31:23 am: Backing up Usage (full database) to: D:\Program Files\Microsoft Sql Server\MSSQL\BACKUP\FULL_(local)_Usage_20060426_103123.sqb 26/04/2006 10:31:23 am: BACKUP DATABASE [Usage] TO DISK = 'D:\Program Files\Microsoft Sql Server\MSSQL\BACKUP\FULL_(local)_Usage_20060426_103123.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', COMPRESSION = 1 26/04/2006 10:31:23 am: Thread 0 error: Process terminated unexpectedly. Error code: -2139684860 26/04/2006 10:31:24 am: Server: Msg 3013 BACKUP DATABASE is terminating abnormally. -------------------------------------------------------------------------------- / comments

SQL Backup log file 26/04/2006 10:31:23 am: Backing up Usage (full database) to: D:\Program Files\Microsoft Sql Server\MSSQL\BACKUP\FULL_(local)_Usage_20060426_103123.sqb 26/04...

0 votes

How can we help you today?

Bernard Sheppard

Comments