SQLMint
Issue:
SQL Server 2016 would not send mail on a new server migration to Windows Server 2016
Solution:
By default, Windows Server 2016 installs .net framework 4.7
The database mail feature needs .Net 3.5
Install this windows feature and this issue gets resolved.
Below is an error that showed up while trying to execute a stored procedure on instance X from SQL server instance y. MYSERVER here represents the name of SQL Server instance X
Msg 7411, Level 16, State 1, Line 1
Server ‘MYSQLSERVER′ is not configured for RPC.
Solution to this was to set RPC in/out to true. Below are the T-SQL commands used.
exec sp_serveroption @server=’MYSQLSERVER′, @optname=’rpc’, @optvalue=’true’
exec sp_serveroption @server=’MYSQLSERVER′, @optname=’rpc out’, @optvalue=’true’
Below shows how to do this graphically , using SSMS – SQL Server Management Studio.
On a server running SQL 2014 SSIS with SSISDB configured, one of the SQL Agent jobs configured to run using a proxy account kept failing with the error below.
Message
Unable to start execution of step 1 (reason: JobOwner domain\domainuser
doesn‘t have permissions to use proxy 1 for subsystem SSIS). The step failed.
Solution that worked for me in my situation.
Query your proxys and see if that proxy is disabled. If so, enable it.
SELECT * FROM msdb.dbo.sysproxies
USE msdb ;
GO
EXEC dbo.sp_update_proxy
@proxy_name = ‘MyProxyUSerUser’,
@enabled = 1;
GO
Issue:
A restored database from one instance to the other keeps showing below when attempting to say, alter a stored procedure.
The database owner SID recorded in the master database differs from the database owner SID recorded in database
Solution applied: Assuming XYZ is the name of the database and contosoadmin is the name of the sa or sysadmin domain account usually assigned as owner in the destination SQL instance. contoso here represents the domain name.
Run:
ALTER DATABASE XYZ SET TRUSTWORTHY ON
ALTER AUTHORIZATION ON Database::archive TO [contosoadmin]
Error “Maximum request length exceeded” in Reporting Services
This error came up while trying to upload a 3.9Mb SSRS report to a new SQL 2008 R2 reporting server.
Solution:
open the web.config file found in:
C:Program FilesMicrosoft SQL ServerMSRS10_50.#####Reporting ServicesReportServer
#### stands for your instance name
Modify line 40 or the line with below:
to:
Restart just the reporting service. There is no need to restart the database service or reboot the server box.
You should now be able to upload reports up to 15000kb ie 15mb in this case. You can modify the value as needed.