Trying to find out if there is any way to do an in place upgrade from SQL 2014 Cluster and upgrade it to SQL 2016 same cluster and if so I cannot find any documents on that I see upgrading SQL 2014 to SQL 2016 which is not that hard but not sure about the cluster or would it be better to build a SQL 2016 Cluster and migrate the databases?
Any help would be appreciated.
Is there a trick to getting this installed correctly? Everything works great until it gets up to starting the service. Here is the complete section of my setup log file.
SQL 2005 Standard.
Machine : KINGSERVER550
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--------------------------------------------------------------------------------
Machine : KINGSERVER550
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_KINGSERVER550_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
Error Number : 29503
I searched a previous thread dealing with this error, but seems like nobody has found a solution.
--Tony
Hi,
What might be the permissions needed for a sql 2017 enterprise install account?
RDP & local admin only?
Anything else?
Hello,
In order to stop using SQL users on our environment we decided to use Windows users. So this is the full picture.
We have AD A and AD B. AD B has the databases (SQL Server 2016) and trusts users from AD A to login.
I have set up windows logins from AD A in the databases in AD B.
The problem is the connectivity is really slow. I do not think this is a bottleneck issue but rather some bad configuration.
To see what happens on the server side I set up an audit and asked a user to login with windows authentication.
I noticed that there are 3-4 login failed whenever he logs in. Also these appear when he tries to do something.
Any tips on improving performance?
Thank you,
Bogdan
Hi All,
Hoping someone can help me
I followed the instructions on installing SQL 2019 on Linux here - > docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver15
I have tried this on multiple distributions
Redhat, AWS Linux 2, Ubuntu, etc
The installation goes smoothly, and the SQL instance works fine however in every case i can't get the SQL Agent started properly.
I have followed the instructions here to enable the agent, after doing
sudo /opt/mssql/bin/mssql-conf set sqlagent.enabled true sudo systemctl restart mssql-server
The sqlagentstartup.log shows the following
Microsoft (R) SQLServerAgent 15.0.1900.25 Copyright (C) 2019 Microsoft Corporation. All rights reserved. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 1 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 2 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 3 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 4 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 5 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 6 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 7 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 8 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 9 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 10 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 11 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 12 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 13 of 15. Will retry again in 1000ms. SQL Agent was not able to connect to SQL Server instance [(local),1433]. Attempt 14 of 15. Will retry again in 1000ms. SQLAgent is exiting
This is the output of sqlagent.out
2 0 1 9 - 1 1 - 1 0 1 4 : 0 7 : 4 7 - ? [ 5 0 8 ] L o g g i n g S Q L S e r v e r A g e n t m e s s a e s i n f i l e ' / v a r / o p t / m s s q l / l o g / s q l a g e n t . o u t ' . 2 0 1 9 - 1 1 - 1 0 1 4 : 0 7 : 4 7 - ? [ 1 0 1 ] S Q L S e r v e r A g e n t s e r v i c e s u c c e s u l l y s t a r t e d 2 0 1 9 - 1 1 - 1 0 1 4 : 0 7 : 4 7 - ? [ 3 5 0 ] W a i t i n g f o r S Q L S e r v e r t o s t a . . . 2 0 1 9 - 1 1 - 1 0 1 4 : 0 7 : 4 9 - ? [ 0 0 0 ] E v e n t G l o b a l \ s q l s e r v e r R e c C o m p t e o p e n e d 2 0 1 9 - 1 1 - 1 0 1 4 : 0 7 : 4 9 - ? [ 5 0 0 ] W a i t i n g f o r S Q L S e r v e r t o r e c e r a l l d a t a b a s e s . . . 2 0 1 9 - 1 1 - 1 0 1 4 : 0 8 : 1 0 - ? [ 1 0 0 ] M i c r o s o f t S Q L S e r v e r A g e n t v e r s n 1 5 . 0 . 1 9 0 0 . 2 5 ( X 6 4 u n i c o d e r e t a i l b u i l d ) : P r o c e s s I D 2 8 2 0 1 9 - 1 1 - 1 0 1 4 : 0 8 : 1 0 - ? [ 4 9 5 ] T h e S Q L S e r v e r A g e n t s t a r t u p r v i c e a c c o u n t i s i p - 1 7 2 - 3 1 - 2 - 3 8 \ i p - 1 0 - 1 0 - 1 4 5 - 1 3 $ . 2 0 1 9 - 1 1 - 1 0 1 4 : 0 8 : 1 0 - ? [ 1 5 1 ] R u n n i n g S Q L S e r v e r A g e n t c r o s p l a t f o r m 2 0 1 9 - 1 1 - 1 0 1 4 : 0 8 : 4 0 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 0 9 : 1 1 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 0 9 : 4 2 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 0 : 1 3 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 0 : 4 4 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 1 : 1 5 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 1 : 4 6 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 2 : 1 7 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 2 : 4 8 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 3 : 1 9 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 3 : 5 0 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 4 : 2 1 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 4 : 5 2 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 2 3 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 4 - ! [ 1 5 0 ] S Q L S e r v e r d o e s n o t a c c e p t t h c o n n e c t i o n ( e r r o r : 1 1 0 0 1 ) . W a i t i n g f o r S q l S e r v e r t o a l l o w c o n n e c t i o n s . O p e r a t i o n a t t e m p t e d w a s : V e r i f y C o n n e c t i o n O n S a r t . 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 4 - ! [ 0 0 0 ] U n a b l e t o c o n n e c t t o s e r v e r ' o c a l ) , 1 4 3 3 ' ; S Q L S e r v e r A g e n t c a n n o t s t a r t 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 4 - ! [ 1 0 3 ] S Q L S e r v e r A g e n t c o u l d n o t b e s a r t e d ( r e a s o n : U n a b l e t o c o n n e c t t o s e r v e r ' ( l o c a l ) , 1 4 3 3 ' ; S L S e r v e r A g e n t c a n n o t s t a r t ) 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 9 - ! [ 2 9 8 ] S Q L S e r v e r E r r o r : 1 1 0 0 1 , T C P P v i d e r : N o s u c h h o s t i s k n o w n . [ S Q L S T A T E 0 8 0 0 1 ] 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 9 - ! [ 1 6 5 ] O D B C E r r o r : 0 , L o g i n t i m e o u t p i r e d [ S Q L S T A T E H Y T 0 0 ] 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 9 - ! [ 2 9 8 ] S Q L S e r v e r E r r o r : 1 1 0 0 1 , A n e t o r k - r e l a t e d o r i n s t a n c e - s p e c i f i c e r r o r h a s o c c u r r e d w h i l e e s t a b l i s h i n g a c o n n e c t i o n t o S Q L S e r v e r . S e r v e r i s n o t f o u n d o r n o t a c c e s s i b l e . C h e c k i f i n s t a n c e n a m e i s c o r r e c t a n d i f S Q L S e r v e r i s c o n f i g u r e d t o a l l o w r e m o t e c o n n e c t i o n s . F o r m o r i n f o r m a t i o n s e e S Q L S e r v e r B o o k s O n l i n e . [ S Q L S T A T E 0 8 0 0 1 ] 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 9 - ! [ 3 8 2 ] L o g o n t o s e r v e r ' ( l o c a l ) , 1 4 3 3 f a i l e d ( D i s a b l e A g e n t X P s ) 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 9 - ? [ 1 0 2 ] S Q L S e r v e r A g e n t s e r v i c e s u c c e s u l l y s t o p p e d 2 0 1 9 - 1 1 - 1 0 1 4 : 1 5 : 5 9 - ? [ 0 9 8 ] S Q L S e r v e r A g e n t t e r m i n a t e d ( n o a l l y )
could anyone please help point me in the right direction here ? is there an issue with the hostname its trying to resolve as (local) ? Am i missing something obvious ?
Cheers
Niro
Hi,
For a 2 node sql availability group: primary and secondary is it essential to have load balancing for high availability?
Thanks.
Hello,
How do I know what is missing and what not in 2017 version?
Is there a full list of 2012 and 2017 that I can compare or does anybody have a better idea ?
Thanks,
rob
oldmandba
Please, does anyone know, how the ISV under ISV Royalty Licensing program gets the access to SQL 2019 installation media and keep? I have to admit, we are ISV Royalty DISTRIBUTOR but have no access to it neither any idea what to do. (MIcrosoft CLT tool does not give any reasonable result)
It looks, Microsoft quite neglects this old-fashioned model of ISV engagement, what would you say?
thanks for any advice
Hello,
We would like to go from SQL Server version 2012 to 2017, but need to know , how big the impact is.
Like the applications build with Visual Studio...which code will fail.
So, I need a nice document that simply shows which objects will be lost or are changed.
Is there such a document ? Or can I make one myself ?
Greetings,
Rob
So I support a Dynamics CRM environment where we have deployed Buffer Pool Extension to expand the buffer pool size for clean pages. This works okay in theory except that I am getting long query times with waits for "EC". Looking around this seems to relate to buffer pool extension waits. I am concerned that while expanding the available buffer pool I have introduced another bottleneck with the BPE.
Looking at the output from querying sys.dm_os_buffer_pool_extension_configuration one of the columns is file_id. To me this would indicate that BPE possibly supports multiple files, like with other database files. Does anyone have any experience with this? All documentation and examples I have seen online only show a single file. I would be interested to see if my current issues could be mitigated with adding multiple files, I just need a way to try it to be able to test.
Joie Andrew "Since 1982"
Hi,
The SQL account needed for dbengine must have these permissions below applied via group policy...They are not available under user rights assignment - so how are they to be applied?
The ones not in the user rights assignment page are:
Hi,
Is it possible to upgrade from SQL server 2016 web edition to SQL server 2017 standard? Can you please let me know how to do it if this is possible?
Thank you,
Ahilan
Hi,
I try to install SQL server 2016 standard on Window server 2016. But fail with error Microsoft.VC80.CRT,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"
How can I fix this problem?
Thank you.Anyone got experience with installing SQL using ansible? I have the following bits in my main.yml file but when try to execute it fails.
<style type="text/css">@page { margin: 2cm } p { margin-bottom: 0.25cm; line-height: 120% } </style>
# Run installer from mounted ISO
- name: Ensure an ISO is mounted
win_disk_image:
image_path: C:\memset\SW_DVD9_NTRL_SQL_Svr_Standard_Edtn_2017_64Bit_English_OEM_VL_X21-56945.ISO
state: present
register: disk_image_out
- debug:
msg: "{{ disk_image_out }}"
- name: Run setup from mounted iso
win_package:
path: '{{ disk_image_out.mount_paths[0] }}\setup.exe'
product_id: 'xxxxx-xxxxx-xxxxx-xxxxx-xxxxx'
state: present
arguments:
- '/ACTION=Install "/ConfigurationFile=C:\memset\SQL_2017_Standard_ConfigurationFile.ini"'
- 'sa_password: "{{ sa_password }}"'
- name: Add or update registry for ip port
win_regedit:
path: HKLM:\Software\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
name: TcpPort
data: 1433
type: string
- name: start a service
win_service:
name: 'MSSQLSERVER'
start_mode: auto
force_dependent_services: yes
state: started
Run failure:
TASK [install-mssql-2017 : Run setup from mounted iso] *****************************************************************************************************************************************
changed: [xxxxxxx]
TASK [install-mssql-2017 : Add or update registry for ip port] *********************************************************************************************************************************
ok: [xxxxxxx]
TASK [install-mssql-2017 : start a service] ****************************************************************************************************************************************************
fatal: [xxxxxxx]: FAILED! => {"changed": false, "exists": false, "msg": "Service 'MSSQLSERVER' is not installed, need to set 'path' to create a new service"}
to retry, use: --limit @/opt/ansible/cache/retry.d/sah_test_install-mssql-2017.retry
PLAY RECAP *************************************************************************************************************************************************************************************
xxxxxxx : ok=12 changed=7 unreachable=0 failed=1
Any ideas why it is failing?
Thanks,
Ahilan
Hi,
Is it possible to upgrade Win 2008 R2 to Win 2012 R2, which already has SQL 2008 R2 installed on it ?
I've read different reports that SQL 2008 R2 service pack 2 or later may or may not need be installed as a prerequisite.
Thanks
AJC999
I cannot install an accessible SQL Server Express Edition on my Ubuntu Server. N.B. I had SQL Server running for ages on my Ubuntu Server but after some months of not using it when I tried to connect this week my attempts to connect from my windows 10 client pc (using SQL Server Management Studio) failed. As such I started from scratch by rebuilding my Ubuntu Server and with such a clean platform then tried to reinstall SQL Server 2017 Express. But connections still failed with the attached error
Investigating the error msg on the web I find this is a known problem with the SQL Server team first stating the fix was to downgrade openssl to release 1.0.2g but I've done this and I still cannot connect. The SQL Server team then updated the link stating the fix was no longer required but installing SQL Server using the instructions provided by the official Microsoft web pages also fails to give me an installation that I can connect to. So I'm stumped and after nearly 20 years of using SQL Server naturally I'm pretty disappointed. Can anyone help me resolve this problem. Remember the Ubuntu Server installation is very minimal, all I've installed is Webmin after the initial Ubuntu Server install.
SQL Server Developer upgrade from 2017 to 2019 failure. I can send the Detail log if needed but it is too large to post here.
Overall summary: