Production database is hosted on a SQL Server Standard instance and is replicated using merge replication with web synchronization to 10 subscriber databases hosted on 10 separate SQL Express server instances. Each subscriber database is accessible by another 5 local users, who can read/write/process the data. SQL Server Standard instance is licensed through CAL scheme. 1. Do we need to have CAL for every of the 5 local users on each subscriber server instance? 2. Do we need to have CAL for every SQL Server Express instance? Web synchronization is achieved through IIS Server on the same server with the SQL Server Standard instance. 3. Do we need to license every SQL Express instance, or it is free for use? 4. There is an additional capability for 20 users, to access the production database directly through a desktop thin client application, where they can read/write/process data, which data are then replicated to every SQL Server Express instance. Do we need CAL for every user of this thin client application? The application is communicating with SQL Server through ODBC using one specific login user credentials. Thanx

There is a modification project in our Process Plant related to SCADA application (Process Automation System) and I am looking for reliable advice/ suggestions from experienced members related to SQL Database Management. **Background:** We have multiple Workstations each running Stand-alone SCADA application with SQL Express for writing Real-time Alarms to SQL DB and occasional reading. We need to forward these Alarms SQL DB (Table only) from all Workstations to Centralized Station, merge all Alarm Tables into one, and then import to SQL Express DB on Centralized Station for Read-Only Purpose. These tasks need to be automated and triggered at appropriate frequency (for eg. every 1 Hour). Please note that all Workstations are Workgroups and Stand-alone. Please also note that communication between Workstations and Centralized Station is strictly uni-directional i.e. Workstation -> Centralized Workstation (so no option for SQL Server Replication). *** ### My Rough Plan #### On Each Workstation: 1. Duplicate the Production_DB to Offline_DB (in same SQL Server Instance) 2. Synchronous/Asynchronous update of Alarms Table from Production_DB to Offline_DB. 3. Periodic Conversion of the Alarms Table from Offline_DB to CSV. 4. Forwarding the CSV to Centralized Workstation. #### On Centralized Workstation: 5. Creating Workstation_DB for each Workstation in SQL Server instance. 6. Converting and importing CSV file in each Workstation_DB to Alarms Table. 7. Creating one Central_DB and merging all Workstations Alarms Table to one Table. 8. Assign Central_DB to SCADA Application on Central Workstation. Please advise if the rough plan needs correction or optimization. I have no background knowledge of SQL scripting and I would be grateful if someone also guide me through the execution of each step in SQL (excluding step 4 and step 8).

We have a partial transactional replication setup in our environment to make a data subset available to another application. Application Server 1 -> Tables1.row1/row2/row3 -> Application Server 2 We are running the same versions of SQL Server everywhere; however, application server 1 is running SQL Server Standard Edition and application server 2 is running SQL Server Express Edition. Server 1 is the publisher and running a push subscription to Server 2. We have a few databases configured exactly as above and they work perfectly. However, I have 2 databases that will not replicate, they get stuck in *"Replicated transactions are waiting for next Log backup or for mirroring partner to catch up."*. We have tried 1448 flag and log backup flags. Running debug on the distributor and subscriber agents shows the following:

-none
OLE DB DISTOLE 'DBSERVER': sp_MSget_last_transaction 
  @publisher_id = 0, @publisher_db = N'DBNAME', @for_truncate = 0x1
Publisher: exec sp_replcounters N'DBNAME'
OLE DB Publisher 'DBSERVER': exec sp_replcounters N'DBNAME'
Status: 16384, code: 22522, text: 
  'Replicated transactions are waiting for next Log backup or for
  mirroring partner to catch up.'.

The distributor is reporting:

-none
 The commit timestamp  value is: 0x0000149100001f30000100000000
 OLE DB Distributor 'DBSERVER': {call sp_MSget_subscription_guid(109)}
 sp_MSget_repl_commands timestamp value is: 0x0x0000149100001f30000100000000
 OLE DB Subscriber 'DBSERVER': 
declare 
    @event_type SMALLINT = 1, 
    @distributor_major_version SMALLINT = 16, 
    @distributor_minor_version SMALLINT = 0, 
    @distributor_build_number SMALLINT = 1000, 
    @totalruntime INT = 23296, 
    @totalworktime INT = 108, 
    @totalnumtrans INT = 0, 
    @numtranspersec REAL = 0.00, 
    @totalnumcmds INT = 0, 
    @numcmdspersec REAL = 0.00, 
    @totalskippedcmds INT = 0, 
    @totalidletime INT = 20015, 
    @agent_id INT = 109, 
    @numtranssincelastevent INT = 0, 
    @numcmdssincelastevent INT = 0, 
    @totalnumbytes BIGINT = 0, 
    @numbytessincelastevent BIGINT = 0 
if object_id(N'sys.sp_repl_generate_subscriber_event') is not null
exec sys.sp_repl_generate_subscriber_event 
    @event_state = @event_type,
    @distributor_major_version = @distributor_major_version,
    @distributor_minor_version = @distributor_minor_version,
    @distributor_build_number = @distributor_build_number,
    @totalruntime = @totalruntime,
    @totalworktime = @totalworktime,
    @totalnumtrans = @totalnumtrans,
    @numtranspersec = @numtranspersec, 
    @totalnumcmd

Looking across the entire environment we have no errors. Communication works perfectly and we have this communication working with other databases. But this database does not want to behave. Any pointers? --- There is nothing using either database, literally no open connections. DBCC OPENTRAN gives the following:

-none
Transaction information for database 'DBNAME'.    
Replicated Transaction Information:    
       Oldest distributed LSN     : (5294:74672:1)    
        Oldest non-distributed LSN : (5294:74680:1)    
DBCC execution completed. 
If DBCC printed error messages, contact your system administrator.    
Completion time: 2024-07-11T16:37:07.0583682+01:00

Transaction information for database 'DBNAME'.

Replicated Transaction Information:
        Oldest distributed LSN     : (5294:74672:1)
        Oldest non-distributed LSN : (5294:74680:1)
DBCC execution completed. 
If DBCC printed error messages, contact your system administrator.

Completion time: 2024-07-11T16:37:07.0583682+01:00

I have a SQL Express 2014 running on a VM with 12 cores SQL Express limitations state that it should be limited to either 4 cores or 1 socket, but when I run this query: > select count(1) "Nb Core used" from sys.dm_os_schedulers where status = 'VISIBLE ONLINE' it returns 8... Here's the result of the query as asked in the comments (Please note that there is no column "socket_count" on that DMV for SQL2014 And here are the information about Core/Socket at OS level: How could that be ? Thank you

I have a SQL Server Express database running on a POS register where the mdf file is 50+gb. When I run select @@version I get: >Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49 Copyright (C) 2017 Microsoft Corporation Express Edition (64-bit) on Windows 10 Enterprise 10.0 (Build 15063: ) I'm confused by this as I thought SQL Server Express has an mdf file limit of 10GB. Is there something I'm missing? SELECT type_desc, physical_name FROM sys.database_files; returns: type_desc|physical_name -|- ROWS|C:\Program Files\Microsoft SQL Server\MSSQL14.POS\MSSQL\DATA\master.mdf LOG|C:\Program Files\Microsoft SQL Server\MSSQL14.POS\MSSQL\DATA\mastlog.ldf I limited the ldf file to about 8GB.

We are building a pseudonymization solution as sort of a proxy between on-prem SQL Server and Azure Data Factory to pull things to the cloud. The pseudonymization parts of it are already on their way but now we are looking into how to query the source databases that this will sit in front of. The plan is to run SQL Server Express in linux containers for the proxy and to use stored procedures for the work. We are looking into OPENROWSET to query the source. We are forbidden to use SQL accounts so we must use AD accounts to connect to the sources. Looking around on the internet I can only find ways to use AD accounts with trusted_connection in SQL Server Express and that I would need to join the container to the AD domain? The configuration parts, drivers and so on that might be needed will be copied into the container when we build it, we will also be copying in some C# built functions to run in SQL CLR. So I am wondering if anybody has an idea on if this can be done and how? We can only run linux containers at the moment and we are only allowed to use AD accounts to connect to the source databases. Is this a problem that can be solved in a good way or should I look at something completely different?

we have sql server express edition 2017 with default instanc ,now we want to upgrade it to Enterprise Licensed Edition 2017 with default instance in the same server At first I thought I had to uninstall express edition but after some search found out that we can upgrade editions What I want > After upgrade will 10GB DB limit in express editon will be gone and apply the Enterprise Edition ? > everything will work as before but with new capabilities of Enterprise edition ? Kindly clear my query ? Thanks

I have developed a database in SQL Server 2022 (and have SSMS), I need to recreate and include all data from that database on a different server which contains SQL Server 2019 Express. When in SSMS, I right click and do a restore it doesn't find my .bak file anywhere. I see the .bak file but it won't find it for me to select. I have moved the filed to multiple locations all in the root of folders I see in the selection window but the file never shows for selection I have also tried to do it via script RESTORE DATABASE [new database name] FROM DISK = 'filelocation\filename.bak' Can anything be done easily where the database gets created inclusive all of the data in each of the tables? I did a restore through SSMS and a direct query and I was expecting that it would create the database, all of the tables. I also created a new database and tried to restore the .BAK file to the newly created database it also didn't work.

I am new to the gis world, and my boss wants me to find a way to automate the process to create back-ups on a local SQL Express DB. I know that I can create one for nonlocal DBs, however, I was wondering if there was a way to also automate at the local level. I haven't been able to find any information on how to create this at all, most posts say it's not for local DBs.Is this true?

We have a SQL Express 2019 server with 3 instances. The VM has 2 sockets each with 2 cores. The SQL Express licensing specifies that a SQL Express **instance** can use the lessor of 1 socket or 4 cores. So far so good. Each instance however is picking socket 0 to use, so all 3 instances are sharing 2 cores while the 2 cores on socket 1 are at idle. Is there a way to assign specific instances to specific sockets? The wording of the license seems to indicate that 3 instances on the same machine could use a total of 12 cores, up to 1 socketx4 cores per instance.

Can you please help me how to execute a stored procedure automatically in SQL database without any transaction in SQL? I want to execute on particular fix time.

Trying to copy a database from a hosted server to a local server for testing purposes and am trying to avoid exporting the whole database as a .bacpac file as there are some tables with tens, maybe hundreds of thousands of rows. I've tried looking for ways to export the database as a .bacpac file using only the top X rows of each database without luck. I have similarly had little luck with exporting the database as a .dacpac file and then transferring a select amount of data between the hosted and local servers.

I would like to use Express instead of Standard. Does Express still have the annoying habit of going to sleep if left unused for a period of time?

I am assisting a client who has recently retired from his original business and is setting up a smaller professional property management partnership. He has been instrumental in setting up a tailored CRM system in the original business, originally in access, and then with a large table running in SQL Server 2017. It has been suggested that he continue development in his new business, using SQL Express. I have created a backup of the 2017 database, and installed SQL Express 2022. To restore the backup to this installation, I need to start Express in single-user mode. I have not succeeded - there are a number of 'system' accounts, eg SQLWriter, Winmanagement, and I can only guess hat one of these manages to log in as the 'single user' before I can log in with my client's local account? Can I temporarily set the various 'system' accounts in some way to enable a restore, and then put them back to their original staus?

I'm developing a service locally that uses SQL Server Express as a database. I'm seeing strange behavior where a stored procedure is executing several times in a row (with different parameters), and after a few successful calls that take ~1 sec each, it starts timing out. The rpc_completed events show the following info: | cpu_time | logical_reads | duration | result | | --------:| -------------:| --------:|:------ | | 984000 | 15244 | 1048445 | OK | | 63000 | 8543 | 75841 | OK | | 531000 | 1782 | 30036796 | Abort | | 0 | 2 | 30003296 | Abort | | 15000 | 820 | 29995839 | Abort | | 0 | 2 | 30010495 | Abort | The four aborted events were retries of the exact same command + parameters. There are several odd things going on here: - cpu_time is always under 1 sec, even when duration jumps to 30 sec - two aborted events show 0 cpu_time and only 2 logical reads (should be thousands) This is just a simple SQL Express instance running on a development machine with nothing else going on. The entire database is only a few MB, so it's hard to image any of these commands being even mildly expensive. So I'm not sure why the server suddenly starts timing out on these commands (while apparently doing almost no work). Any idea what's going on here? **UPDATE 1:** - I ran the failed command a bit later from a query window and it executed successfully in ..." StatementType="SELECT" QueryHash="0x358148098B8FEF90" QueryPlanHash="0xF78E3AAD5E94ED14" RetrievedFromCache="true" SecurityPolicyApplied="false"> ... --> ... --> ``` I can see there's a small (269 ms) ASYNC_NETWORK_IO wait, probably just SSMS being a bit slow pulling/displaying the query results, but I don't see where the other 14 seconds came from. Query elapsed time in the actual plan is only 375 ms, while the connection elapsed time 15 sec. **UPDATE 3:** I checked sys.dm_exec_session_wait_stats for info on the SPID for the above execution (63), and got these numbers: |session_id|wait_type|waiting_tasks_count|wait_time_ms|max_wait_time_ms|signal_wait_time_ms| |--|--|--|--|--|--| |63|PAGELATCH_SH|2|0|0|0| |63|PAGELATCH_EX|4|0|0|0| |63|SOS_SCHEDULER_YIELD|194|1|0|1| |63|MEMORY_ALLOCATION_EXT|9189|21|3|0| |63|RESERVED_MEMORY_ALLOCATION_EXT|390|0|0|0| |63|**ASYNC_NETWORK_IO**|**219**|**13787**|**1307**|**8**| Looks like I found the missing 14 sec for the manual execution from SSMS (not sure why this wasn't mentioned in the actual query plan WaitStats), but I'm not sure if the original timeouts when the service was trying to execute this command had the same cause. I'm suspicious of some obscure SQL Server Express limit being the cause, but I can't find any limits that looks relevant. **UPDATE 4:** Red herring. Looks like the ~15 sec execution time in SSMS is just due to requesting the actual execution plan. Happens every time. Disable that option and the execution time is consistently < 1 sec.

I have a SQL Express 2014 instance on a server with 1 database that has 1 table. I would like to move that database to an existing SQL Server 2019 Standard instance that is on a different server. The windows server version of the Express instance is 2012R2, the windows server version of the SQL Standard version is 2019, both are 64-bit. I'm a SQL newbie. Can someone point me to a how-to guide that tells me how to move that sql express database? All I've been able to find are instructions for upgrading the SQL server, not moving a database to an existing server.

I have SQL Server Express 2019 on my local system on a large SSD with >50Gb free disk space. I had a 14Gb database on production, which I copied, deleted a bunch of old data, and reduced the size below 10G, backed up and restored it on my local system. With some use, the local database then auto grew to 10G but still has a bunch of free space. Now it has started giving me the insufficient disk space error when inserting a record in for some tables (not all which is so weird): > Could not allocate a new page for database 'MyDB' because of > insufficient disk space in filegroup 'PRIMARY'. Create the necessary > space by dropping objects in the filegroup, adding additional files to > the filegroup, or setting autogrowth on for existing files in the > filegroup. When I run the shrink database command, it just clears the log and does not release the free space in the data file. I have tried a variety of ways. It seems like the shrink database command itself needs some space and not getting it even thought the data file has a lot of space. Any ideas?

Parallel redo is shutdown for database '' with worker pool size . Parallel redo is started for database '' with worker pool size . Starting up database '' I see this on a client PC a lot in the Windows Event Viewer (Event Id 49930 or 17137). This is a regular Windows PC, not a server, with a default instance of SQL Server 2017 Express Edition and SSMS. What is that parallel redo? Here's the output from the error log:

2019-05-28 12:23:03.360	spid16s	A self-generated certificate was successfully loaded for encryption.
2019-05-28 12:23:03.360	spid16s	Server is listening on [ 'any'  1433].
2019-05-28 12:23:03.360	spid16s	Server is listening on [ 'any'  1433].
2019-05-28 12:23:03.360	spid16s	Server is listening on [ 'any'  50374].
2019-05-28 12:23:03.360	spid16s	Server is listening on [ 'any'  50374].
2019-05-28 12:23:03.360	spid16s	Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\FOLLOWIN ].
2019-05-28 12:23:03.360	spid16s	Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$FOLLOWIN\sql\query ].
2019-05-28 12:23:03.360	spid16s	Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-05-28 12:23:03.360	Server	SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2019-05-28 12:23:03.360	spid16s	SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-05-28 12:23:03.370	Server	The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/pcFoo:FOLLOWIN ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-05-28 12:23:03.370	Server	The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/pcFoo:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-05-28 12:23:03.430	spid17s	A new instance of the full-text filter daemon host process has been successfully started.
2019-05-28 12:23:03.520	spid12s	Starting up database 'mssqlsystemresource'.
2019-05-28 12:23:03.520	spid21s	Starting up database 'Foobar'.
2019-05-28 12:23:03.520	spid20s	Starting up database 'msdb'.
2019-05-28 12:23:03.530	spid12s	The resource database build version is 14.00.3162. This is an informational message only. No user action is required.
2019-05-28 12:23:03.550	spid12s	Synchronize Database 'master' (1) with Resource Database.
2019-05-28 12:23:03.550	spid21s	Parallel redo is started for database 'Foobar' with worker pool size .
2019-05-28 12:23:03.560	spid12s	Starting up database 'model'.
2019-05-28 12:23:03.560	spid21s	Parallel redo is shutdown for database 'Foobar' with worker pool size .
2019-05-28 12:23:03.580	spid12s	Synchronize Database 'model' (3) with Resource Database.
2019-05-28 12:23:03.590	spid12s	Polybase feature disabled.
2019-05-28 12:23:03.590	spid12s	Clearing tempdb database.
2019-05-28 12:23:03.670	spid12s	Starting up database 'tempdb'.
2019-05-28 12:23:03.710	spid20s	Synchronize Database 'msdb' (4) with Resource Database.
2019-05-28 12:23:03.710	spid21s	Synchronize Database 'Foobar' (5) with Resource Database.
2019-05-28 12:23:03.710	spid22s	The Service Broker endpoint is in disabled or stopped state.
2019-05-28 12:23:03.710	spid22s	The Database Mirroring endpoint is in disabled or stopped state.
2019-05-28 12:23:03.730	spid22s	Service Broker manager has started.
2019-05-28 12:23:03.730	spid6s	Recovery is complete. This is an informational message only. No user action is required.
2019-05-28 12:28:21.180	spid51	Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-05-28 12:28:21.180	spid51	Using 'xplog70.dll' version '2017.140.3162' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2019-05-28 12:28:21.320	spid51	Starting up database 'Foobar'.
2019-05-28 12:28:21.340	spid51	Parallel redo is started for database 'Foobar' with worker pool size .
2019-05-28 12:28:21.350	spid51	Parallel redo is shutdown for database 'Foobar' with worker pool size .
2019-05-28 12:28:21.360	spid51	Starting up database 'Foo'.
2019-05-28 12:28:21.380	spid51	Parallel redo is started for database 'Foo' with worker pool size .
2019-05-28 12:28:21.400	spid51	Parallel redo is shutdown for database 'Foo' with worker pool size .
2019-05-28 12:28:21.410	spid51	Synchronize Database 'Foo' (6) with Resource Database.
2019-05-28 14:27:21.430	spid59	Starting up database 'Foo'.
2019-05-28 14:27:21.450	spid59	Parallel redo is started for database 'Foo' with worker pool size .
2019-05-28 14:27:21.470	spid59	Parallel redo is shutdown for database 'Foo' with worker pool size .
2019-05-28 14:27:21.480	spid59	Starting up database 'Foobar'.
2019-05-28 14:27:21.500	spid59	Parallel redo is started for database 'Foobar' with worker pool size .
2019-05-28 14:27:21.510	spid59	Parallel redo is shutdown for database 'Foobar' with worker pool size .
2019-05-28 14:27:38.330	spid59	Starting up database 'Foobar'.
2019-05-28 14:27:38.360	spid59	Parallel redo is started for database 'Foobar' with worker pool size .
2019-05-28 14:27:38.370	spid59	Parallel redo is shutdown for database 'Foobar' with worker pool size .
2019-05-28 14:27:40.010	spid59	Starting up database 'Foo'.
2019-05-28 14:27:40.050	spid59	Parallel redo is started for database 'Foo' with worker pool size .
2019-05-28 14:27:40.080	spid59	Parallel redo is shutdown for database 'Foo' with worker pool size .
2019-05-28 14:28:04.160	spid59	Starting up database 'Foo'.
2019-05-28 14:28:04.180	spid59	Parallel redo is started for database 'Foo' with worker pool size .
2019-05-28 14:28:04.210	spid59	Parallel redo is shutdown for database 'Foo' with worker pool size .
2019-05-28 14:28:10.620	spid52	Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2019-05-28 14:28:10.690	spid52	Using 'xpstar.dll' version '2017.140.3162' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2019-05-28 14:28:14.220	spid52	Starting up database 'Foo'.
2019-05-28 14:28:14.240	spid52	Parallel redo is started for database 'Foo' with worker pool size .
2019-05-28 14:28:14.270	spid52	Parallel redo is shutdown for database 'Foo' with worker pool size .
2019-05-28 14:28:14.410	Backup	Database backed up. Database: Foo, creation date(time): 2019/05/08(15:06:00), pages dumped: 2555, first LSN: 48:9778:37, last LSN: 48:9795:1, number of dump devices: 1, device information: (FILE=2, TYPE=DISK: {'C:\Users\Joe\Documents\Backup Followin\Foo_FULL_05272019_235209.BAK'}). This is an informational message only. No user action is required.
2019-05-28 14:28:14.420	Backup	BACKUP DATABASE successfully processed 2546 pages in 0.112 seconds (177.529 MB/sec).
2019-05-28 14:28:19.120	spid53	Starting up database 'Foo'.
2019-05-28 14:28:19.140	spid53	Parallel redo is started for database 'Foo' with worker pool size .
2019-05-28 14:28:19.160	spid53	Parallel redo is shutdown for database 'Foo' with worker pool size .
2019-05-28 14:28:20.610	spid59	Starting up database 'Foo'.
2019-05-28 14:28:20.650	spid59	Parallel redo is started for database 'Foo' with worker pool size .
2019-05-28 14:28:20.670	spid59	Parallel redo is shutdown for database 'Foo' with worker pool size .
2019-05-28 14:28:31.030	spid54	Using 'dbghelp.dll' version '4.0.5'

0.3162.1 (X64)

May 15 2019 19:14:30

Copyright (C) 2017 Microsoft Corporation

Express Edition (64-bit) on Windows 10 Pro 10.0  (Build 17763: )

I started a dozen attempts to install the SQL Server Management Studio for the 2008 Express Version of SQL Server. What i use: Windows Vista 2007 SP 2 What i did: a) I downloaded the install file SQLManagementStudio_x86_DEU.exe from [Microsoft's Download Center](http://www.microsoft.com/downloads/de-de/details.aspx?FamilyID=08e52ac2-1d62-45f6-9a4a-4b76a8564a2b) b) I started the setup and chose "Installation"/"Adding Feature" c) The feature selection appears, but I can chose only from SQL Client Connectivity SDK d) This is wrong I guess; but even if I click next I get an error message like "Please chose a feature first" What can I do? Thanks for any advice!!!

I've got a user that wants to install SQL Server Express 2014 on his Windows 10 laptop. The default installation fails: 2017-11-13 13:39:31.31 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Feb 20 2014 20:04:26 Copyright (c) Microsoft Corporation Express Edition (64-bit) on Windows NT 6.3 (Build 10586: ) 2017-11-13 13:39:31.31 Server UTC adjustment: 1:00 2017-11-13 13:39:31.31 Server (c) Microsoft Corporation. 2017-11-13 13:39:31.31 Server All rights reserved. 2017-11-13 13:39:31.32 Server Server process ID is 5868. 2017-11-13 13:39:31.32 Server System Manufacturer: 'Dell Inc.', System Model: 'Latitude 7280'. 2017-11-13 13:39:31.32 Server Authentication mode is WINDOWS-ONLY. 2017-11-13 13:39:31.32 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG'. 2017-11-13 13:39:31.32 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required. 2017-11-13 13:39:31.32 Server Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\mastlog.ldf 2017-11-13 13:39:31.32 Server Command Line Startup Parameters: -s "SQLEXPRESS" -m "SqlSetup" -Q -q "SQL_Latin1_General_CP1_CI_AS" -T 4022 -T 4010 -T 3659 -T 3610 -T 8015 -d "C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Template Data\master.mdf" -l "C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf" 2017-11-13 13:39:31.58 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2017-11-13 13:39:31.58 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2017-11-13 13:39:31.58 Server Detected 16265 MB of RAM. This is an informational message; no user action is required. 2017-11-13 13:39:31.58 Server Using conventional memory in the memory manager. 2017-11-13 13:39:31.66 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033) 2017-11-13 13:39:31.69 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled. 2017-11-13 13:39:31.73 Server Query Store settings initialized with enabled = 1, 2017-11-13 13:39:31.74 Server The maximum number of dedicated administrator connections for this instance is '1' 2017-11-13 13:39:31.74 Server This instance of SQL Server last reported using a process ID of 8668 at 11/13/2017 1:39:30 PM (local) 11/13/2017 12:39:30 PM (UTC). This is an informational message only; no user action is required. 2017-11-13 13:39:31.74 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2017-11-13 13:39:31.75 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2017-11-13 13:39:31.77 Server Database Mirroring Transport is disabled in the endpoint configuration. 2017-11-13 13:39:31.77 Server Software Usage Metrics is disabled. 2017-11-13 13:39:31.77 spid8s Warning ****************** 2017-11-13 13:39:31.78 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required. 2017-11-13 13:39:31.78 spid8s Starting up database 'master'. 2017-11-13 13:39:31.79 spid8s 1 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required. 2017-11-13 13:39:31.80 spid8s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required. 2017-11-13 13:39:31.89 Server CLR version v4.0.30319 loaded. 2017-11-13 13:39:31.94 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2017-11-13 13:39:31.94 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2017-11-13 13:39:31.98 spid8s SQL Trace ID 1 was started by login "sa". 2017-11-13 13:39:31.98 spid8s Server name is 'SWSTW10WRBRT\SQLEXPRESS'. This is an informational message only. No user action is required. 2017-11-13 13:39:32.00 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 2017-11-13 13:39:32.04 spid14s The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x80090331. Check certificates to make sure they are valid. 2017-11-13 13:39:32.04 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 2017-11-13 13:39:32.04 spid14s Error: 17182, Severity: 16, State: 1. 2017-11-13 13:39:32.04 spid14s TDSSNIClient initialization failed with error 0x80090331, status code 0x80. Reason: Unable to initialize SSL support. The client and server cannot communicate, because they do not possess a common algorithm. 2017-11-13 13:39:32.04 spid14s Error: 17182, Severity: 16, State: 1. 2017-11-13 13:39:32.04 spid14s TDSSNIClient initialization failed with error 0x80090331, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The client and server cannot communicate, because they do not possess a common algorithm. 2017-11-13 13:39:32.04 spid14s Error: 17826, Severity: 18, State: 3. 2017-11-13 13:39:32.04 spid14s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 2017-11-13 13:39:32.04 spid14s Error: 17120, Severity: 16, State: 1. 2017-11-13 13:39:32.04 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. Will he have to manually create a certificate, or is there a way to disable the SSL requirement during the installation? The installation is for local testing purposes only, so security isn't a concern. Thanks! Oli