Current SQL Server:
SQL Server 2016 Express SP1
Microsoft SQL Server 2016 (SP1-CU7-GDR) (KB4057119) - 13.0.4466.4 (X64)
Dec 22 2017 11:25:00
Copyright (c) Microsoft Corporation Express Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 15063: )
Downloaded Cumulative Update 1 and went through the installation steps
Downloaded Microsoft .NET Framework 3.5
Database Mail still does not show. Suggestions?
Of note, when I click on the download file for Microsoft .NET Framework 3.5, it doesn't do anything even when trying to run as an Administrator.
Thank you!
http://www.sqlservercentral.com/blogs/querying-microsoft-sql-server/2013/09/02/sending-mail-using-sql-server-express-edition/
In SQL server standard and enterprise edition,A DataBase mail functionality in built to sent mail.But in SQL Server express edition,You need either use CLR integration or configure SQL Mail using MSDB system database.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/cd59b9cc-21ea-4130-afd1-791124031ada/can-sql-server-express-send-emails?forum=sqlexpress
You can make use of CLR Integration for sending email from SQL Server Express.
http://www.sqlservercentral.com/articles/SQL+Server+Express/71341/
http://www.vnypatel.com/sending-emails-with-clr-sql-server-express-editions
SQL Server Express does not support database mail.
https://msdn.microsoft.com/en-us/library/cc645993.aspx
Related
I have an issue because SQL Server Launchpad service does not start because SQL Server instance and Launchpad is different versions. How I could upgrade SQL Launchpad service?
When I download and start cummulative update it shows me SQL Server is version
Microsoft SQL Server 2019 (RTM-CU16-GDR) (KB5014353) - 15.0.4236.7 (X64) May 29 2022 15:55:47 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows 10 Pro 10.0 (Build 19044: ) (Hypervisor)
If I choose SQL Launchpad in update installation it also appear to be 15.0.4236.7
But in SQL Server Configuration manager it shows 15.0.2000.5
Is there any way to solve it? or only downgrade the SQL Server?
Thank you
For our production DB, we are on the following SQL version,
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
From Microsoft KB:
https://support.microsoft.com/en-sg/help/3135244/tls-1-2-support-for-microsoft-sql-server
This SQL Server version is lower than the first build that supports TLS 1.2,
I don't think it supports TLS 1.2.
Can anyone confirm this?
I'm comparing the version numbers 10.0.5500.0 vs 10.50.6542.0 (minimum build that supports TLS 1.2)
SQL Server 2008 v10.0.5500.0 is SQL Server 2008 with Service Pack 3 (SP3) applied. SQL Server with a version number 10.50.xxx.xxx would be SQL Server 2008 R2 - and yes, that's a different version (not just a service pack) of SQL Server.
If you look further down in that document you linked, there's also a line for SQL Server 2008:
SQL Server 2008 SP4 10.0.6547.0
So you would need to apply SP4 to your SQL Server 2008 instance (and possibly also that update that is linked in your document) in order for it to support TLS 1.2
I'm running this version of SQL Server on an Azure instance:
Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49
Copyright (C) 2017 Microsoft Corporation
Web Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)
Per the description for the instance ('SQL Server 2017 Web on Windows Server 2016'):
This image contains the Web edition of SQL Server 2017 on Windows Server 2016. This provides a low-cost database solution for medium-size web applications. It includes the core database engine and Management Studio for integrated administration and development. Also includes basic versions of Reporting Services for web reports, Integration Services for moving and transforming data, and Analysis Services for data mining. We recommend that you use a virtual machine size of DS12 or higher.
When I attempt to connect / configure using the 'Report Services Configuration Manager', I'm unable to 'find' the Report server instance in the 'Reporting Services Configuration Connection' dialog. I.e. the 'Report Server Instance' had not values to choose from.
I installed Microsoft SQL Server 2017 Reporting Services (note three editions were available - Eval, Developer, & Express - tried each edition - uninstalling each version before trying the next)
When I went to configure the Reporting Services using the 'Report Server Configuration Manager' I got to the 'Change Database' tab. At the point that I am assigning the database engine to the reporting services I get the error:
The database engine instance you selected is not valid for this edition of report server
Note I'm running the Web edition of SQL Server, but I'm not seeing an option to select that in the installation of the report services
Thoughts re what I'm missing?
I Ended up reverting back to SQL 2016 to go around the issue
I have been having a similar issue. I tried to get the SQL Server key from a PowerShell script as well, but they didn't work for SQL Server 2017 Web Edition.
So the solution was much easier than I expected.
Go to the C: drive of your VM. You will find SQL Setup there.
Run the setup to start a new standalone installation. When you will be on product key page it will display the License Key.
Copy that key and put it into your Reporting Services Installation.
I hope it will help someone.
The error is basically saying you cannot use the edition of your SQL Server Engine (in this case, Web edition) for SQL Server Reporting Services 2017. Can you try a different edition of SQL Server?
Update:
You can learn more about supported editions of Database Engine you can use for each different type of edition of Reporting Services 2017 at https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-features-supported-by-the-editions-of-sql-server-2016. While some of the content may not be applicable for SSRS 2017, the bits which are applicable are still accurate.
While restoring database I got this error
SQL Server cannot load database 'XXX' because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports Change Data Capture.
Mine SQL Server
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (Intel X86) Jun 28 2012 08:42:37 Copyright (c) Microsoft Corporation Express Edition with Advanced Services on Windows NT 6.1 (Build 7600: )
I know there is no feature of CDC in Express Edition but i got XXX.bak file which i need to restore on my sql server. Is there any way of script to remove CDC feature from the file?
I have to copy a db from a remote server to my local dev machine.
What is the best way to do it.
Last night I made a script for the remote db using xSQL Object and ran it on the local server. the script gave a bunch of errors. Below is the select ##version output for the 2 servers. is there a reason the script is not working
The remote server is using SQL server authentication, the local one is using windows authentication
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64)
Jul 9 2008 14:17:44
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 2)
It would be helpful if your provided some of the errors your script produced.
I notice you're using Enterprise and Express editions - these two editions have differing features, described here: http://www.microsoft.com/sqlserver/2008/en/us/editions.aspx. Perhaps you're using a feature that Express edition doesn't support, or your database is too big.
Not sure if the functionality is exactly the same in 2008, but in 2005, you can open up SQL Management Studio, right-click on the dbase you'd like to copy, and then click on Export Data.
This will guide you through a wizard, allowing you to export the data to another SQL dbase, including one that runs on your local machine. Used it many times - works great.
Why don't you just do a backup and restore?