AdminMicrosoft SQL Server
(Admin, Microsoft Azure)
My feedback
-
4 votes
Upvotes: 1
<=-=Nov 7 2017 1:53PM=-=>thanx for the report! Does this still reproduce for you, and perhaps on 17.3?
<=-=Nov 7 2017 8:00PM=-=>Confirmed, still a bug in 17.3, exactly the same. Even on Add Range.
AdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
1 vote
Repro:
1. Connect to an Azure SQL DW instance (though any version should produce the same results)
2. Click on Generate Script
3. Go through steps within the dialogue box
4. Find that the wizard is in a never-ending loop -
1 vote
In the first case:
EXEC sp_execute_external_script @language = N’Python’,
@script = N’import re, pandas
Ret = InputDataSet
Ret[“an”] = pandas.Series([re.sub(”[^0-9]”, “”, i) for i in Ret[“an”]], index = Ret.index, dtype = “int32″)‘,
@input_data_1 = N’SELECT an FROM alphanum’,
@output_data = N’Ret’we would treat @output_data as a user defined parameter and expect the params clause. There is no way for us to know whether @output_data is a misspelling of @output_data_1_name or the user wants a parameter @output_data.
There are two issues in the second example:
EXEC sp_execute_external_script @language = N’Python’,
@script = N’import re, pandas
Ret = InputDataSet
Ret[“an”] = pandas.Series([re.sub(”[^0-9]”, “”, i) for i in Ret[“an”]], index = Ret.index, dtype = “int32″)‘,
@input_data_1 = N’SELECT an FROM alphanum’,
@output_name = N’Ret’,
@params = N’@Ret int’@params should be before @output_name and should contain the declaration of the @output_name parameter, not the value N'Ret'. Something like:
EXEC sp_execute_external_script
@language = N'Python',
@script = N'...',
@input_data_1 = N'SELECT an FROM alphanum',
@params = N'@output_name nvarchar(max)',
@output_name = N'Ret' -
3 votes
Thank you for reporting this. This will be fixed in the next CU for SQL Server 2016 SP2.
-
4 votes
Does this happen consistently or only the first initiation of SSMS?
Also, please share version info for SSMS/SSIS and what instances they are connecting to so we can figure this out.thanks,
DinakarAdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
1 vote
Upvotes: 1
Could you validate if the issue exists with the latest version of SSMS - 17.9.1 and post back?
Also, please validate with SSMS 18 Preview 5.thanks
DinakarAdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
8 votes
Upvotes: 51
<=-=Nov 11 2014 11:50AM=-=>I agree with Keith. I also manage multiple SQL Server instances. This is a persistent annoyance for nearly the last decade.
<=-=Jan 6 2015 1:21PM=-=>The bug is over 10 years old. The SSMS team keeps saying they can’t reproduce it. It feels like they never actually use their product.
Problem seems to occur more frequently when you store multiple remote servers. It’s probably very reproducible once you have 3 remote servers stored.
Microsoft did try to contact me directly and use LiveMeeting to my computer. If I recall right, Microsoft couldn’t get LiveMeeting to work and then they pretty much abandoned attempting to fix this and claimed they cant repro it. I was working with chandrag@microsoft.com .
<=-=Mar 7 2015 10:05AM=-=>This issue is so annoying. My SSMS 2014 remembered my DB’s password for maybe 2-3 weeks and it hasn’t remembered it since…
We made some improvements in this area for SSMS 18.
Could you see if you can repro the issue with the latest Preview 5?thanks,
DinakarAdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
4 votes
Upvotes: 6
Do you get any syntax error when creating Certificates or Keys?
Thanks,
DinakarAdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
2 votes
How did you install SSMS 17.9? Was it a full install on a clean machine (i.e. with no prior versins of SSMS 17.x) or it was an upgrade from some older versions of SSMS 17.x?
If you upgraded, did you use the “Full 17.9 package” or the “Upgrade package”?
Aside from that, could you try to uninstall and reinstall and let us know if that addresses the issue?
Please update your SSMS to 17.9.1 (the latest as of this post) and repro the scenario. If you are still seeing issues, please post back and we can review.
thanks,
Dinakar -
4 votes
The error you report indicates that we are unable to read the Vulnerability Assessment rule store which is embedded as a resource in one of the SqlServer module’s dlls.
Unfortunately, we have been unable to reproduce this error. Perhaps you can provide some more information on how to reproduce. Specifically:
1. What environment are you running on? Are there any special restrictions applied to your PowerShell environment?
2. Have you tried on other machines? Does it reproduce there too?
3. Are you running just the Invoke-SqlVulnerabilityAssessmentScan cmdlet or is something taking place before that? What happens when you just run the one command?
4. Any other information that you think may be pertinent to reproducing?
Thanks -
2 votes
If I close SSMS uncleanly with documents open, I get a dialog asking me if I want to recover or not. I can choose not to recover some or all of them. Are you saying this dialog takes too long to load, or is not being shown?
Also, I think you can turn off auto recover altogether in tools\options\AutoRecover
-
2 votes
so this is a bit lame but in SSMS 17.x you need to set this environment variable to the DNS suffix of blob storage for the cloud you want: AZUREBLOBDNSNAME
The default is blob.core.windows.net.
For US Government cloud I think you would set AZUREBLOBDNSNAME environment variable to "blob.core.usgovcloudapi.net"I think this is fixed in the SSMS 18 preview, can you try it there?
-
91 votes
CMS (RegisteredServers) has been ported. It will be included in the next version of SMO and/or the next version of the SQL Powershell module.
-Matteo
this is the current list from the v18 NuGet
Microsoft.SqlServer.ConnectionInfo.dll
Microsoft.SqlServer.Management.Dmf.dll
Microsoft.SqlServer.Management.Sdk.Sfc.dll
Microsoft.SqlServer.Management.SmoMetadataProvider.dll
Microsoft.SqlServer.Management.XEvent.dll
Microsoft.SqlServer.Management.XEventDbScoped.dll
Microsoft.SqlServer.Management.XEventDbScopedEnum.dll
Microsoft.SqlServer.Management.XEventEnum.dll
Microsoft.SqlServer.Smo.dll
Microsoft.SqlServer.SmoExtended.dll
Microsoft.SqlServer.SqlEnum.dll -
3 votes
Upvotes: 1
We are looking into this one.
AdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
6 votes
Upvotes: 2
There's a devious way to change the server name in the connection dialog - switch to the Additional Connection Parameters tab and add "Data Source=servername,portnumber"
That may not unblock this entire scenario, though.AdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
3 votes
-
2 votes
Upvotes: 15
Do you happen to know if visual studio 2013/2015 exhibit the same behavior?
AdminMicrosoft SQL Server
(Admin, Microsoft Azure)
shared this idea
·
-
21 votes
this item could be combined with this one: https://feedback.azure.com/admin/v3/suggestions/33531871/activity
-
4 votes
maybe this item becomes combined with this one: https://feedback.azure.com/admin/v3/suggestions/33532654/activity
-
35 votes
Hi, thanx for the feedback.
As Ben points out, if you know which fields on the Database object you need, you can use Server.SetDefaultInitFields to make sure the collection is initialized with all those fields in the first query.Is there a particular scenario, using the latest SMO NuGet, where use of SetDefaultInitFields isn’t sufficient to speed up the query noticeably?
If you have an Intellitrace or XEvents trace I could use for reference it’d be a great help.we've made changes to the "bad query" in recent versions of SMO to improve the worst case time. Previous versions where joining on DMVs like db_hasaccess and such that really slowed things down. Do you see any improvement in recent SMO NuGet package versions?
Please try with latest GA - 17.9.1 or 18 Preview 6 and post back if you still see the issue.