AdminMicrosoft SQL Server
(Product Manager, Microsoft Azure)
My feedback
-
4 votes
-
31 votes
Thanks for the clarification. We'll keep this open for future votes.
-
123 votes
Issue has been identified and a fix is being made. It will be rolled out with the next update of SSMS 18.
Thanks,
-Matteohi all
We are planning the next update in the next few weeks. thanks for your patience.
-
3 votes
hello JM
all the tools for Azure Data are listed under Tools section - https://docs.microsoft.com/en-us/sql/tools/overview-sql-tools?view=sql-server-2017
including SQLServer module. I agree with you that most database servers are not connected to the internet. However, in our experience and in our discussions with customer, typically customers have a process for this. Such as a shared folder/site that hosts all the company approved downloads from servers to OS to tools that the company employees download from instead of every individual having to download the same tool over and over.
Having said that, we have been discussing about a "Tools pacakge" internally. Will share once we have more concrete details around it.
thank you for the feedback.
Dinakar
-
1 vote
Have you always used SSMS to configure your system? I.e. not other tools or straight T-SQL? Is it a coincidence that for both columns you have a value of 14420? Is that a value you recall explicitly setting?
From what you are telling me, it looks like SSMS is assuming that 14420 is a number of days (as opposed to a number of minutes), hence it can’t handle it because “it is too big”).
More investigation going on…
Thanks,
-Matteo -
44 votes
I’m looking into this issue.
In the meanwhile, could you take a look at the SSMS setup logs (%TEMP%\SSMSSetup\SSMS-Setup-ENU_20190430231104.log). I’m interested in the lines in the range 133-216. Could you share those (tip: have a look at the lines and sanitize them, if you think they may contain sensible information?
Also, if you could share the output of:
reg query “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32 /sAnd, finally, to unblock yourself:
1) Make sure you don’t have any previous version (RC, Preview) of SSMS 18.0 installed (check Add/Remove programs; if you do, uninstall it)
2) Make sure “C:\Program Files (x86)\Microsoft SQL Server Management Studio 18” does not exist (if it does, the delete it)
3) Delete the mentioned registry key (e.g. by running from an elevated cmd prompt:
reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32)
4) Retry setup
Please, let…@leniel: When you say "also", do you mean in addition to do or as a separate issue? Let's try not to mix possibly unrelated issues.
The issue you are seeing is most likely because your setup, despite the fact that it claimed to have succeeded, did not - and possibly files are missing or corrupt. Did you try to uninstall and reinstall?
@diklevich: could you also try to uninstall and reinstall and report back?
@daniel.yu: you could be running into https://feedback.azure.com/forums/908035/suggestions/37502512. Could you update that thread with info like: OS, Hotfixes installed on the machine (do you have all the latest critical updates?). I'm currently suspecting an issue in NetFx4.7.2, which I was able to resolve by installing the latest hotfixes (though that was good on Windows 7 SP1). I'm interested in knowing if people are seeing that issue on other OSes.
Thanks,
-MatteoCan you uninstall all versions of SSMS, reboot, and proceed with a clean install of SSMS 18 please?
-
24 votes
We are looking into why disabling the setting is not persisting over restart of SSMS.
In the meantime, as a workaround, can you validate if Tools > Options > Text Editor > Transact-SQL> uncheck "Auto list members" works?
It seemed to work for me..hi folks
The setting works in a New Window, after you make the change (enable/disable).
Are you saying its not working in the new window?I have tried on multiple machines and it works as expected for me..
-
4 votes
This is indeed an unintended removal. It only affected SQLEXPRESS.
Thanks for the reporting it.
We’ll fix it in a future release of SSMS 18.×.hi Samrat
Are both Import Data and Export Data disabled? or just one of them?
thanks,
Dinakar -
9 votes
Hello
Please use Debugging feature in SSDT. TSQL Debugging has been deprecated for now.AdminMicrosoft SQL Server
(Product Manager, Microsoft Azure)
shared this idea
·
-
8 votes
Sorry folks, but we are not able to repro this issue (either using SSMS 17.9.1 or SSMS 18 Preview 7).
Since multiple people out there are reporting this issue, it is obvious that we are missing something that is specific to your environment or configuration.
Could you help us out and try to describe a little better your subscription/environment/account/permissions?
For example, does the following mainstream scenario works for you all:
1) Connect to Azure Portal
2) Create SQL server+database
3) Go to SSMS and connect to
4) Add firewall ruleIf it does, then can you identify what is different between the case where it works and the case where it does not?
Thanks,
-MatteoPlease try with latest GA - 17.9.1 or 18 Preview 6 and post back if you still see the issue.
AdminMicrosoft SQL Server
(Product Manager, Microsoft Azure)
shared this idea
·
-
3 votes
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' -
4 votes
Thank you for reporting this. This will be fixed in the next CU for SQL Server 2016 SP2.
-
5 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
(Product Manager, Microsoft Azure)
shared this idea
·
-
4 votes
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
(Product Manager, Microsoft Azure)
shared this idea
·
-
5 votes
Upvotes: 6
Do you get any syntax error when creating Certificates or Keys?
Thanks,
DinakarAdminMicrosoft SQL Server
(Product Manager, Microsoft Azure)
shared this idea
·
-
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
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?
-
103 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
(Product Manager, Microsoft Azure)
shared this idea
·
-
7 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
(Product Manager, Microsoft Azure)
shared this idea
·
Thank you for the feedback. This issue will be addressed in an upcoming SQL Server 2019 CU. Tentatively CU2.