Comments
Sort by recent activity
Probably because when a PK is dropped all other indexes featuring the PK IDs have their "secret columns" removed as the table is now a heap.
Like I said. "I could be wrong" but that was how I understood the behavior to work. / comments
Probably because when a PK is dropped all other indexes featuring the PK IDs have their "secret columns" removed as the table is now a heap.
Like I said. "I could be wrong" but that was how I under...
Thanks Brian.
For completeness, the table in question contains about 110MM rows, which takes considerably longer to alter with the NCI in place.
Haven't yet got the hang of migration scripts in SSC - too much else going on to spend time on them, to be honest, so I keep my scripts in sequence in the file system and run them manually. Thankfully with only one target production server per application, it's not arduous.
Best regards,
Stephen / comments
Thanks Brian.
For completeness, the table in question contains about 110MM rows, which takes considerably longer to alter with the NCI in place.
Haven't yet got the hang of migration scripts in SSC...
Thanks Aaron, installed and makes a lot more sense. Tried several partial matches on wide tables and everything looks good. Appreciate the swift turnaround. / comments
Thanks Aaron, installed and makes a lot more sense. Tried several partial matches on wide tables and everything looks good. Appreciate the swift turnaround.
I must admit to being surprised by the volume of what I will call "noise" listed above potential columns that are partially matched.
Thinking about the context of the SQL Prompt suggestions, when one is writing a SQL WHERE clause, how frequently is a column in a FROM clause the actual subject of the WHERE versus some obscure system function, another table name (huh?), or a function? I'd suggest that in excess of 95% of the time the COLUMN is what is wanted... It is acknowledged BAD PRACTICE to use functions in WHERE clauses anyway, or so I believe.
I'm out of votes on SQL Prompt (two logins' worth), so may I here suggest:
Provide an option to "always list columns in suggestion lists, even partial matches, above any functions of any kind".
In over 25 years of coding SQL, I can safely say the number of times I want a built-in or sys. function as the FIRST artifact after my WHERE is 0.05% of the time, or less!
Doesn't "columns first" simply just make sense? Or maybe I really am missing something... / comments
I must admit to being surprised by the volume of what I will call "noise" listed above potential columns that are partially matched.
Thinking about the context of the SQL Prompt suggestions, when o...
Yesterday's script:
INSERT INTO dbo.t_company_custom_def
( custom_id
, custom_company_id
, custom_xml
, update_date
, update_by
)
SELECT @NewID
, 30
,[custom_xml]
, '20140305 15:45'
, 'me'
FROM [xcp_ref].[dbo].[t_company_custom_def] ccd
WHERE co
First off, having completed the WHERE and a space, it gave me ccd, the alias, as expected, and correct. I typed c and the ccd alias reamined at the top, followed by columns, so I typed an o, to get to "WHERE co" as in the code above. That's when the whole list changed to a list of f(x) functions, headed by COALESCE, then CONTAINS, then a bunch of tables (I have them listed by schema), then a slew of sys.functions, and I don't see the "custom_COmpany_id" (in the enlarged pop-up) that I expected my CO typing to bring to the top of the list. SQL Prompt at this point becomes useless for rapid code completion.
I would really like to send you a SnagIt or Snip, but Windows8.1 has completely destroyed my ability to use them. I hope you can create a simple table like the above, and reproduce the problem...
Failing that, a remote diagnostic session would be fine by me. / comments
Yesterday's script:
INSERT INTO dbo.t_company_custom_def
( custom_id
, custom_company_id
, custom_xml
, update_date
, update_by
)
SELECT @NewID
, 30
...
Attributes used to come first for WHERE clauses - now they are last and that's highly counterproductive. I get other table then function names before columns. Is it just me? Using the 188 build, win8.1 x64, SQL2012EE / comments
Attributes used to come first for WHERE clauses - now they are last and that's highly counterproductive. I get other table then function names before columns. Is it just me? Using the 188 build, w...
Option to turn OFF bracket-matching, please?
I find that SSMS Intellisense limited to code blocks and bracket-matching works extremely well with SQL Prompt. I wouldn't like to see the two products argue over who will highlight a bracket, or not.
Thanks. / comments
Option to turn OFF bracket-matching, please?
I find that SSMS Intellisense limited to code blocks and bracket-matching works extremely well with SQL Prompt. I wouldn't like to see the two products...
I'm having a conversation with OnTime Developers on Tuesday, so will wait until, and if, there is more detailed info I can add on Uservoice.
I recommended the SSMS Ecosystem initiative to the OnTime folks - hoping it bears fruit as they already have a plugin for Visual Studio. / comments
I'm having a conversation with OnTime Developers on Tuesday, so will wait until, and if, there is more detailed info I can add on Uservoice.
I recommended the SSMS Ecosystem initiative to the OnTim...
As I just bumped into the same issue and am NOT IIS6 cognisant, may I request that the documentation at http://documentation.red-gate.com/display/SM4/Using+SQL+Monitor+with+IIS be updated as the wizard description is not what is shown in my IIS6 environment, especially as there is absolutely no mention of the bolded "Allow anonymous access to this Web site" at point 3.f.
The only reason why the problem may be traced to a credential issue is if one uses the Test Connection button and sees within the output that there's a yellow warning triangle - it shows the message below:
The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.
The THIRD sentence holds the clue: "Application Pool", "Physical Path", so methinks "maybe the 'Connect as...' should be the App Pool login?" - YEP!
One hour spent chasing down an issue I probably need not have had for an Upgrade exercise that is really and truly, in IIS6 terms, a nigh fresh install. / comments
As I just bumped into the same issue and am NOT IIS6 cognisant, may I request that the documentation at http://documentation.red-gate.com/display/SM4/Using+SQL+Monitor+with+IIS be updated as the wi...
File posted via email to the 10148 incident.
Thanks, Peter. / comments
File posted via email to the 10148 incident.
Thanks, Peter.