How can we help you today? How can we help you today?
WeeeBob

Activity overview

Latest activity by WeeeBob

feature suggestion: Code sniffing
Just a wee suggestion that I think would fit into SQL prompt quite well. Hows about Code sniffing? For checking code compliance with user defined standards. Like checking column names conform to a ...
2 followers 2 comments 0 votes
Why are you using Ctrl + Enter ?? shouldn't you be using Ctrl + Space if you want to manually trigger suggestions? Drop Table Ctrl+space works fine, but I too get the problem with Ctrl+Enter with version 5.3.6.28 in SSMS 2008r2 / comments
Why are you using Ctrl + Enter ?? shouldn't you be using Ctrl + Space if you want to manually trigger suggestions? Drop Table Ctrl+space works fine, but I too get the problem with Ctrl+Enter with ...
0 votes
[image] Just installed SQL prompt 5.1.6.35 , and it caused same problems with VS2008 crashing out when trying to preview SQL2008R2 report. Disabled as described above and at least I can get on with my work now!! / comments
Just installed SQL prompt 5.1.6.35 , and it caused same problems with VS2008 crashing out when trying to preview SQL2008R2 report. Disabled as described above and at least I can get on with my wor...
0 votes
I don't think that can be the case, as this problem tends to appear after I have ran SQL Compare to ensure the two db's schemas are in sync. So how could there be incompatible data types? then every so often when you go into the SQL data compare and try running its gets this error. Yesterday the events ran a little like this: run SQL compare to bring our UAT inline with the DEV database. used SQL compare to apply the changes, was only 3 columns that had been added to a table in DEV, so the compare script was just to add these to the UAT table Run SQL data compare to check for static data changes. error! now the table that had the DDL changes, is not a table that is actually selected for the data compare ? so why would you get fieldmappings suddenly becoming invalid? is there some refresh problem in data compare when the DDL has been updated? Our standard way to roll changes out now is to use SQL compare to sync the DDL between the two, then run SQL data compare on a subset of tables (all fairly static lookup tables) to sync up any data changes. Usually works very well, but every so often this problem pops up and it just makes it a pain to recreate the data compare project, espiecally as I have to go through and reselect only the tables we want and switch to some custom keys. If you could improve the actual error data compare is returning to tell what field mappings are invalid that it would certainly help! the logs are useless for trying to gleam anything either from what I've seen. / comments
I don't think that can be the case, as this problem tends to appear after I have ran SQL Compare to ensure the two db's schemas are in sync. So how could there be incompatible data types? then ever...
0 votes
Extreme Video corruption with Quadro FX1700 Video cards ??
Hi, I recently changed my video cards in my precision T7400, to dual Nvidia Quadro FX1700 's so I could use three monitors. Trouble is I now get some wonderful video corruptions when SQL prompt app...
1 follower 1 comment 0 votes
Shortcut keys no longer work? and 'funny' version
When I downloaded SQL Prompt (and SQL refactor) to do my 14 day trial. I'm sure there where shortcut keys to do important things, like CTRL+ B +L to layout sql. I recently downloaded and installed ...
2 followers 2 comments 0 votes