User profile for PDinCA

Not a synonym. It's a user table in the database SSMS is set to: USE <dbname>. <dbname>.dbo.t_user_ref is the fully qualified table name. I'm fully authorized to the instance as a member of sysadmin. This happens very frequently. Synonym suggestion is OFF and has been since 5.3 was installed - it's of little use to me until columns are supported. / comments

Not a synonym. It's a user table in the database SSMS is set to: USE <dbname>. <dbname>.dbo.t_user_ref is the fully qualified table name. I'm fully authorized to the instance as a member of sysadm...

0 votes

Believe this is the one: http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggestions/suggestions/1712949-suggestions-missing-for-longer-t-sql-code / comments

Believe this is the one: http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggestions/suggestions/1712949-suggestions-missing-for-longer-t-sql-code

0 votes

I hunted for about 20 minutes but have given up as every time I use the "back" browser feature the list of posts I searched for is gone. I forgot which words I used to search before posting the defect. Anyway, besides it being a "ghost" suggestion, it is still a very real bug. Please pursue the bug, not the ghost [image] Apologies for the apparent misdirect. / comments

I hunted for about 20 minutes but have given up as every time I use the "back" browser feature the list of posts I searched for is gone. I forgot which words I used to search before posting the de...

0 votes

Hi Chris, I just created an SP in SSMS and saved per my usual encoding. Having tested it, I dragged it into SQL Multi Script and made one change, from ALTER to CREATE, then ran it against my remai...

0 votes

UCS-2 Little Endian (whatever that is :? ) / comments

UCS-2 Little Endian (whatever that is :? )

0 votes

Local OS is Windows Server 2003 R2 Standard, SP2 SSMS: Microsoft SQL Server Management Studio 10.50.2500.0 Microsoft Analysis Services Client Tools 10.50.1600.1 Microsoft Data Access Components (MDAC) 3.86.3959 Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 Microsoft Internet Explorer 8.0.6001.18702 Microsoft .NET Framework 2.0.50727.3625 Operating System 5.2.3790 How does one ascertain the encoding, please, as there's nothing in the tools==> options dialog that I can see? Thanks for picking this up, Chris. / comments

Local OS is Windows Server 2003 R2 Standard, SP2 SSMS: Microsoft SQL Server Management Studio 10.50.2500.0 Microsoft Analysis Services Client Tools 10.50.1600.1 Microsoft Data Access Compon...

0 votes

Entire DB schema emailed with pointer to the SP I was editing at the time. / comments

Entire DB schema emailed with pointer to the SP I was editing at the time.

0 votes

Further to our email thread, I bumped the look-back to 50000 and restarted SSMS (2008R2 vintage under WinServer2003EE). <ParserLookBackDistance>50000</ParserLookBackDistance> <ParserLookAheadDistance>3000</ParserLookAheadDistance> I edited the usp_CacheDelete SP and at the penultimate line shown below tried to add to the JOIN - NO SUGGESTIONS from m. /* ----------------------------------------------------------------------------- ** Delete t_meter_agg rows ** -------------------------------------------------------------------------- */ DECLARE @DELETED TABLE ( Site_ID int NOT NULL , Tag_ID int NOT NULL , Input_ID int NOT NULL , StartTime datetime NOT NULL , EndTime datetime NOT NULL , IntervalCode nvarchar(5) NOT NULL ) DELETE ma OUTPUT DELETED.agg_site_id , DELETED.agg_tag_id , DELETED.agg_input_id , DELETED.agg_start_time , DELETED.agg_end_time , DELETED.agg_interval_code INTO @DELETED FROM dbo.t_meter_agg ma INNER JOIN @METER m ON m.SiteID = ma.agg_site_id AND m.TagID = ma.agg_tag_id AND m. WHERE ma.agg_end_time > m.StartTime / comments

Further to our email thread, I bumped the look-back to 50000 and restarted SSMS (2008R2 vintage under WinServer2003EE). <ParserLookBackDistance>50000</ParserLookBackDistance> <Pars...

0 votes

PDinCA wrote: Further to our email thread, I bumped the look-back to 50000 and restarted SSMS (2008R2 vintage under WinServer2003EE). <ParserLookBackDistance>50000</ParserLookBackDistance> <ParserLookAheadDistance>3000</ParserLookAheadDistance> Having bumped the lookback to 100,000 BYTES, I now see the suggestions AND the SP's Parameters. TWO things: 1. If having the DEFAULT set to a pitifully low 5000 eventuates in so much frustration, not only for me, WHY is it set so LOW? 2. Given this is an SP of a mere 250 LINES, and my largest, due to it's inescapable complexity, is currently over 2600 LINES (175,773 CHAR), with other very complex SPs at 1400+ LINES, what should my lookback value be set at, please? I absolutely NEED the entire SP to be covered by the abilities of SQL Prompt's suggestions mechanism... Given that, as you said Chris, in your email, UTF-8 vs. UTF-16 makes a difference, please: 1. Enhance SQL Prompt so it recognizes the encoding and sets a default lookback value based on 1- or 2-bytes per visible character. 2. Consider significantly increasing the default lookback to support at least a 250 LINE SP, that, in my case, uses DOS\Windows encoding and is ONLY 8705 characters in total length. 3. Fix what appears to be a lookback BUG that requires me to set the value to 100,000 BYTES for a file that can only be 2x8705 BYTES raw max size. Perhaps SQL Prompt's lookback needs to consider what the SSMS script editor does to files presented to it, including what a user's custom background color may entail, so that the byte-count is realistic. To replicate my SSMS environment, I use a custom color background of RGB 252/253/204, which is much more restful on the eyes than stark white, IMO, and Lucida Console 8pt. Even at 50,000 BYTES lookback, my 8705 CHAR file still couldn't elicit a suggestion at line 183, CHARACTER 6,768, which appears to point to a defect in SQL Prompt somewhere... / comments

PDinCA wrote: Further to our email thread, I bumped the look-back to 50000 and restarted SSMS (2008R2 vintage under WinServer2003EE). <ParserLookBackDistance>50000</ParserLookBackDistan...

0 votes

An error has occurred. Try refreshing the page: the problem may be temporary.Error details http://localhost:8080/static/3.0.0.1575/Scripts/RedGate.Response.js: 324 Failed Cleared up by using Chrome - and yes, FASTER PAGE LOADS is better [image] / comments

An error has occurred. Try refreshing the page: the problem may be temporary.Error details http://localhost:8080/static/3.0.0.1575/Scripts/RedGate.Response.js: 324 Failed Cleared up by using Chr...

0 votes

How can we help you today?

PDinCA

Comments