Hello,
We have a Production Database running on SQL Server 2008 Standard Edition R2 and now we would like to upgrade to SQL Server 2017 Web Edition.
Is it possible to upgrade? If yes, pls let me know the best practice to upgrade to SQL 2017 Web Edition and the best possible approach.
Regards,
Preeth
Does anyone know what operating systems I can run SQL Server 2012R2 on and it be supported by MS?
Thanks
Hey,
I'm dealing for days now with a strange behaviour of the 'msodbcsql_17***.msi'. If I do a silent install of this MSI as part of a chained msi of an InstallShield 'Basic MSI' Setup, I can't configure the ODBC driver (create a DSN) after successfull installation. Eventlog logs: "eventid 1, ...maybe the installation of this component is corrupt...". Even doing a 'Repair' install does niot help.
The strange thing: If I install the same MSI Package by doubble clicking (with full UI) on the same system all is functional fine.
The cmdline parameters used for installing as chained MSI are: /qn /i"<...>\msodbcsql_17.4.1.1_x64.msi" IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=SQL_SQLODBC_CORE APPGUID="{BF95F113-EEE5-4AA4-B71D-53CDF0F8D9A1}"
But even without the "ADDLOCAL" und "APPGUI" properties it's the same problem. Without the "IACCEPTMSODBCSQLLICENSETERMS" property the install fails (as documentated).
Did anyone here managed to install this silent and it's functional after that?
Thanks in advance for any tip.
Ron
Hi,
I am trying to apply patch "SQLServer2016SP2-KB4052908-x64-ENU" on one of the SQL server instance but when the process bar goes on 90%, the SQL Server resources wend down (this is an active/passive cluster environment) with a message that patch has failed and check the log fine.
Following is the log file details. Any help would be appreciated and the Directory on H drive is there.
Overall summary:I got workstation which is Windows 10 Enterprise Version 1803. Recently vulnerability scan gives me the following critical finding that said unsupported version of SQL server version is running.
My most concern is I have never installed SQL server to the workstation. This is client machine and workstation for development, and it is installed SQL Server Management Studio version 17 in this workstation to connect to DB server, but not installed SQL Server application itself. The finding looks like not about general SQL Server or SQL Serer Express, and it is about SQL Server Express LocalDB, and I think this unsupported version is originally came from installing Visual Studio Professional 2015 version 14 Update 3 to this workstation, but I am not sure yet, so I would like to ask a couple of questions.
(1) Is my understanding correct that when you install Visual Studio, it also installing SQL Server Express LocalDB automatically as well?
(2) How can I upgrade version of SQL Server Express LocalDB to 13.0.4001.0?
Any advise will be gratefully appreciated. Thank you..
Hi,
I need to upgrade MS SQL Standard Edition to Enterprise Edition. Details are below:
1. Current MS SQL Edition and Version : MS SQL Server 2012 R2 Standard Edition.
2. Windows machine details where current DB is running : Windows Server 2012 R2
3. Enterprise Version details to be upgrade : MS SQL Server 2012 R2 Enterprise Edition.
4. Current System: One active and other passive mode
My requirement is to upgrade Active-Standby current structure to Enterprise version.
Please help me how can I do this in step by step way, please also suggest if it is required to take DB backup and Roll back plan.
Please also suggest how does the upgrade of edition works on 2 node cluster with SQL ServerFailover Cluster?
Thanks
Hi All,
We recently applied hotfix KB450522 to our MS SQL SERVER 2016, and we are having issues with high cpu usage, things are 2 to 6 times slower. We tried uninstalling the patch but the high CPU issue remains. We then decided to install the latest CU, CU8, Nothing changed we are still seeing high CPU usage and slow performance. Has anyone else had this happen? Does anyone have any suggestions on what to do?
Does anyone know?
The Microsoft Life cycle support page does not provide any information for such
I got Windows 10 workstation that installed Visual Studio 2015 Professional with SQL Server Express 2016 LocalDB. Recently vulnerability scan give me the following critical finding. I need to upgrade the SQL server Express to version 2015.131.5101.9
As following to my research, I though the following Microsoft page is the one to upgrade it because it is written exactly same file version number in the Summary section.
Description of the security update for SQL Server 2016 SP2 GDR: July 9, 2019
It cannot connect to internet from my workstation, so I download a patching for standalone from Microsoft Catalog below as following to the section [Method 2: Microsoft Update Catalog] in the above link.
Security Update for SQL Server 2016 Service Pack 2 GDR (KB4505220)
I could completed to install the patch, but the version of the setup.exe that vulnerablity scan mentioned is not changed after the patching and reboot.
C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\SQLServer2016\setup.exe
Does anyone know how to upgrade the version of the setup.exe file to 2015.131.5101.9? Any advice will be gratefully appreciated it.
Hi. I got Windows 10 workstation that got installed Visual Studio 2015 Professional. I just found out when I installed the visual studio, it also installed "SQL server LocalDB" with it. I need to upgrade the version of the "SQL server LocalDB" to the supported version as following to the latest scan result of vulnerability scan to my workstation.
My concern is I am not really sure what SQL Server LocalDB is. It seems like small database for local development with C#/visual studio. Here are my question I need some help...
(1) Is SQL Server LocalDB is different with SQL Server Express?
(2) If I need to upgrade the version of the SQL Server LocalDB, should I download the latest version of "SQL server Express"? I found the link to download from Microsoft page, but I am not sure this can be used for upgrading the LocalDB..
SQL Server 2017 Express edition
If there is anything wrong on my understanding, please correct me. Any advice will be gratefully appreciate it. Thank you.
Hi,
I am getting below error while installing SQL Server 2016 with SP2 (Slipstream) on Windows Server 2016. Please help if you have faced similar issues.
Error Screenshot:
Bootstrap log:
We have planned to SQL Server upgradation from SQL Server 2012 RTM version to SQL Server 2012 SP4 version.
Before implementing the change we have executed the SQL Server 2012 Upgrade Advisor Tool in the server and we are facing below error in the tool.
"SQL Server version: 11.00.2100 is not supported by this release of Upgrade Advisor, only SQL2005, SQL2008 or SQL2008 R2 is supported."
So which version of Upgrade Advisor Tool version should be used before upgradation from SQL Server 2012 RTM version to SQL Server 2012 SP4 version.
We have planned to SQL Server upgradation from SQL Server 2012 RTM version to SQL Server 2012 SP4 version.
can we upgrade the sql server 2012 RTM version to SQL Server 2012 SP4 version directly using the kb 4018073 which is used for upgrading from sql server 2012 SP3 to SP4 or we have do it step from RTM to SP1 , SP1 to SP2 , SP2 to SP3 , SP3 to SP4
Please suggest us how to complete it in one step.
Hey All,
I am new to administrating SQL servers and have been tasked with enabling change data capture after all the data one of our critical tables was somehow deleted. I was directed to this link by a coworker, but he has never enabled CDC before and wished me good luck. The document has helped me get to the point where I am ready to enable CDC on the table itself, but I am confused about the gating roles setting and how to configure it for my users. I would like to make it so that anyone with the ability to write to the table is tracked, but I don't want to limit myself to only those people in that role. I would like admins to be tracked as well for security reasons.
Here is an example of the command I need to execute:
USE MyDB GO EXEC sys.sp_cdc_enable_table @source_schema = N'database1', @source_name = N'dataTable', @role_name = N'MyRole', @supports_net_changes = 1 GO
Should I worry about specifying the gating role, or should I list it as NULL? Does NULL apply the tracking to everyone or no one? Also, I may have to apply this to multiple tables. Can I chain the tables in the source name or should I run this command for each table?
Thank you for your help and I look forward to your responses.
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hi
Our current SQL server setup runs with 3 X Windows 2016 servers in failover cluster with 2 X SQL instances. All applications refer the SQL by "Instace\SQLSrvrName". Our management asks to migrate all these clustered instances to SQL high availability model because of various including limitation with backup to take clustered hosts. We never configured SQL high availability, looking for an option to migrate the clustered / multiple instance SQL to high availability with minimum downtime. Also it's hard to change the SQL server reference in all apps, so if possible we have to keep the same format even after migrating to SQL HA model.
Thanks in advance
LMS
Hi,
For a user with local admin rights, is there any difference to run SQL setup As Admin vs runnig the setup without this option? I read somewhere in the past that we should never run the setup with 'As Admin' option, I am installing SQL with 'As Admin' option and never face any issue, do you know a case when this could generate an issue or this is just a myth ?
Best regards
Hi,
Recently we have upgraded our production instance from SQL server 2008 to SQL Server 2017. All Query and Stored procedures are running fine except one query is running slow in new instance after up-gradation. In SQL Server 2008 the query takes 7 minutes to execute but in 2017 it takes 50 minutes to executes.
If I change the compatibility level of the 2017 instance to 100 (2008) then the query take 7 minutes to executes.
I need to keep the database compatibility level 140 (2017). Is there any way I can run this particular query with compatibility level 2008.
I saw some site trace flag '9481' can be enable in SQL Server 2014 to run query behave like 2008. Is there any similar trace flag for SQL Server 2017?
Or is there any way to export the query plan from SQL Server 2008 instance and import to SQL Server 2017?
Regards
Arif
Hi,
I know the mechanics of how I upgrade a 2017 Express install to 2017 Standard and have the key and licence.
I'm not envisaging any issues, however are there any gotchas or caveats that I should be aware of from someone who has done this?
thanks!
Greetings!
I am in the process of upgrading all of my servers from Server 2008R2 to Server 2012 as a transitional step to eventually getting my shop to Server 2016.
One of my servers is running SQL Server 2008R2 (10.50.6560). I am thinking that I should upgrade the Windows Server to 2012 first before upgrading SQL Server. Is this OK?
Thanks,
Ken
Ken Carter