How can we help you today? How can we help you today?
Oliwa
I hit the TAB key. So I type... SELECT<TAB><TAB>*<ENTER> FROM<TAB><TAB>dbo.MyTable<ENTER> where<TAB><TAB>1 = 1; My insertion keys for SQL Prompt at ENTER and TAB. Everything else is unchecked. / comments
I hit the TAB key. So I type... SELECT<TAB><TAB>*<ENTER> FROM<TAB><TAB>dbo.MyTable<ENTER> where<TAB><TAB>1 = 1; My insertion keys for SQL Prompt at ENTER and TAB. Everything else is unchecked.
0 votes
Sql Prompt works for me with VS SP1 installed. For some reason the menu was disabled in SSMS, but the autocomplete still worked. I uninstalled Sql Prompt and reinstalled it and all is good again. / comments
Sql Prompt works for me with VS SP1 installed. For some reason the menu was disabled in SSMS, but the autocomplete still worked. I uninstalled Sql Prompt and reinstalled it and all is good again.
0 votes
petey wrote: Does the SQL Backup Agent service startup account have rights to that network share? Yes...everyone has access to that share. / comments
petey wrote: Does the SQL Backup Agent service startup account have rights to that network share? Yes...everyone has access to that share.
0 votes
Yes, my styles are set to UPPERCASE for all 3 options (keywords, functions, and types). This works fine in SSMS but not in VS. I do not have those style options because I am using Standard Edition. / comments
Yes, my styles are set to UPPERCASE for all 3 options (keywords, functions, and types). This works fine in SSMS but not in VS. I do not have those style options because I am using Standard Edition.
0 votes
I tried what you suggested and whenever I had very simple scripts the capitalization worked fine, but I know I have scripts where "go" doesn't capitalize. I will respond with more information when I encounter the behavior again. / comments
I tried what you suggested and whenever I had very simple scripts the capitalization worked fine, but I know I have scripts where "go" doesn't capitalize. I will respond with more information when...
0 votes