Comments
Sort by recent activity
I second those suggestions / comments
I second those suggestions
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.
I figured it out. You have to put the <DATABASE> tag on the folder and not the file. / comments
I figured it out. You have to put the <DATABASE> tag on the folder and not the file.
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.
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.
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...
I do not have any objects starting with "go". Next time it happens I'll see if there is any objects named similarly. / comments
I do not have any objects starting with "go". Next time it happens I'll see if there is any objects named similarly.
I think I found a reproducible scenario...
This is just one of the scenarios I found where go is not capitalized. There are others, but sometimes they work and other times not.
If I declare a variable and type go afterward it capitalizes like so... DECLARE @var INT;{ENTER}
go{ENTER}
Now if I try putting in a USE statement before or after the batch go does not capitalize... USE master;{ENTER}
go{ENTER}
DECLARE @var INT;
GO
USE master;{ENTER}
go{ENTER}
But if I type "g" and hit ENTER it works. / comments
I think I found a reproducible scenario...
This is just one of the scenarios I found where go is not capitalized. There are others, but sometimes they work and other times not.
If I declare a vari...
Yes, all options are set to uppercase. All other keywords capitalize as expected. If I type a "g" and hit ENTER it inserts "GO", and if I type "select" and hit TAB it capitalizes, but not "g".
And I have TAB and ENTER set as activation keys. / comments
Yes, all options are set to uppercase. All other keywords capitalize as expected. If I type a "g" and hit ENTER it inserts "GO", and if I type "select" and hit TAB it capitalizes, but not "g".
An...
I actually don't, I want the format of the insert to be like this... INSERT dbo.PortfolioServicingType
(
PortfolioID
, ServicingTypeID
)
VALUES (
0 -- PortfolioID
, 0 -- ServicingTypeID
)
But since I don't think the Standard version will do that putting it all on one line makes it easier for me to format how I want it. / comments
I actually don't, I want the format of the insert to be like this...INSERT dbo.PortfolioServicingType
(
PortfolioID
, ServicingTy...