Copy SSIS Package Between Database Servers

Export SSIS Package Open up SSMS -> Integration Services Catalogs -> SSISDB -> Projects -> Export This should create a .ispac file. Import SSIS Package Copy over the .ispac file to new server. Double click on the .ispac file to start the Integration Service Deployment Wizard. Select “Project deployment file” and set the “Path” to... » read more

Deploy SSIS to SQL Server

Copy Deployment File to SQL Server File Type Note MyPackage.dtsx Integration Services Package MyPackage.SSISDeploymentManifest Integration Services Deployment Manifest Double click to launch Package Installation Wizard MyPackageInterfaceConfig.xml XML Configuration Document Select “SQL Server deployment” and check “Validate packages after installation” Enter “Server name”, Use Windows Authentication, and “Package path”, check “Rely on server storage for encryption”.... » read more

Error 1069: The service did not start due to a logon failure

Error: Could not start the <service name> service on Local Computer. Error 1069: The service did not start due to a logon failure. Resolution: Service account might be disabled. Try using another service account. Sources: https://www.codetwo.com/kb/troubleshooting-error-1069-the-service-did-not-start-due-to-a-logon-failure-for-sent-items-update/

Always On Database Stuck in Restoring State

Issue: Always On database stuck in “Restoring” state after setting up Always On Fix: Go to Always On High Availability -> Database -> “Join to Availability Group” Sources: https://www.mssqltips.com/sqlservertip/5460/sql-server-database-stuck-in-restoring-state/

TEXTIMAGE_ON

Indicates that the text, ntext, image, xml, varchar(max), nvarchar(max), varbinary(max), and CLR user-defined type columns (including geometry and geography) are stored on the specified filegroup. TEXTIMAGE_ON is not allowed if there are no large value columns in the table. TEXTIMAGE_ON cannot be specified if <partition_scheme> is specified. If “default” is specified, or if TEXTIMAGE_ON is not specified... » read more

SSPI handshake failed

Error SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon attempt failed Alert SQL Server Log

SQL Server Import and Export Wizard Tool

To import/export between Staging and Production server, use the SQL Server Import and Export Wizard Tool. Use “SQL Server Native client 11.0” Use query to import data to a temporary table and then insert into the destination table from the temporary table. 30 million records = 10 minutes to import data from source table to... » read more