Activity overview
Latest activity by dmckinney
The supplied snippet is "SELECT * FROM".
I modified this to include a space at the end, thus "SELECT * FROM ", thinking it might make my life easier.
Reading this post, I now realise that whereas, before, my tapping space would trigger the list of table names, now, with the space included in the snippet, I have to additionally Ctrl-space to make the same list appear.
Perhaps you're seeing something like this?
Hope I make sense! / comments
The supplied snippet is "SELECT * FROM".
I modified this to include a space at the end, thus "SELECT * FROM ", thinking it might make my life easier.
Reading this post, I now realise that whereas, ...
Anu,
The issue is that the schema_name function takes a int - schema_id - as input parameter, and returns - as the name suggests - a string (sysname). it DOES NOT return an int, as the tooltip states.
If you look up schema_name in books online, you can see this, and if you compare with the tooltip text in sql prompt for the same function, you can hopefully understand my question.
Thanks and regards,
David. / comments
Anu,
The issue is that the schema_name function takes a int - schema_id - as input parameter, and returns - as the name suggests - a string (sysname). it DOES NOT return an int, as the tooltip sta...
tooltip meta data for schema_name
I don't know where sql prompt gets its meta data for the tooltips which are displayed when using functions but curiously....
...it says that schema_name returns an int!
This doesnt really bother me...
Bug in "Qualify Object Names" introduced bug in my code!
SELECT onfile.DealReference
dbo.DCA_Detail AS onfile
WHERE onfile.DealReference NOT IN (
SELECT DealReference
...
Why not just use visual studio?
I've been a happy and regular user of SQL Compare for a number of years. However my boss doesn't want to renew the licenses as he says Visual Studio (certain editions) can offer all the same funct...
No particular reason.
In this post you publish a 'description' of the xml file. IMO Normal practice would be to publish the schema.
Among the benefits of the schema approach is that if you do make modifications to the xml and it subsequently doesn't work, you can validate against the xsd schema, and often this will tell you where you've broken it. (Depending on the tool, you may also benefit from intellisense etc..)
But basically I just find it a very bizarre design choice, which is hard to explain. / comments
No particular reason.
In this post you publish a 'description' of the xml file. IMO Normal practice would be to publish the schema.
Among the benefits of the schema approach is that if you do make...
I'm very surprised to see the chosen xml tag naming conventions (Object0..., Object1..., Object2...). This makes it impossible to provide a schema - and I'd be amazed if there was a valid technical reason for this choice(?).
Any plans to remedy this?
(Also foreign is spelled incorrectly (foriegn) )-: ) / comments
I'm very surprised to see the chosen xml tag naming conventions (Object0..., Object1..., Object2...). This makes it impossible to provide a schema - and I'd be amazed if there was a valid technica...
Document All objects - command line support.
I'd like to use the command line option to periodically redocument databases. I note however that the objects to be documented are explicitly listed in the .sqldoc xml document. (I'm not sure the...