SQL Server

SQL Server TSQL Get Last Identity Seed After Insert

Wed, 09 Nov 2022 02:11:47 GMT

Use SCOPE_IDENTITY() if you are inserting a single row and want to retrieve the ID that was generated.

CREATE TABLE #a(identity_column INT IDENTITY(1,1), x CHAR(1));

INSERT #a(x) VALUES('a');

SELECT SCOPE_IDENTITY();

Result:

----
1

Use the OUTPUT clause if you are inserting multiple rows and need to retrieve the set of IDs that were generated.

INSERT #a(x) 
  OUTPUT inserted.identity_column 
  VALUES('b'),('c');

Result:

----
2
3

source:

https://dba.stackexchange.com/questions/124847/best-way-to-get-last-identity-inserted-in-a-table

Command Line equivalent of Generate Scripts Wizard in SQL Server Management Studio (SSMS)

Tue, 04 Oct 2022 06:55:26 GMT

https://github.com/microsoft/mssql-scripter

Visual Studio 2022 Extensions Now Available for Reporting Services and Analysis Services

Fri, 12 Aug 2022 07:32:39 GMT

https://devblogs.microsoft.com/visualstudio/analysis-services-and-reporting-services-extensions-for-visual-studio-2022-are-here/?ocid=AID3031635&utm_issue=August2022

Steps for Installing SQL Server AlwaysOn Availability Groups

Wed, 15 Jun 2022 11:39:00 GMT

Prerequisites

Windows

Do not install AlwaysOn on a domain controller
The operating system must be Windows 2012 or later
Install all available Windows hotfixes on every server (replica)
Windows Server Failover Cluster (WSFC) must be installed on every replica

SQL Server

Each server (replica) must be a node in the WSFC
No replica can run Active Directory services
Each replica must run on comparable hardware that can handle identical workloads
Each instance must run the same version of SQL Server, and have the same SQL Server collation
The account that runs SQL Services should be a domain account

Network

It is recommended to use the same network links for communication between WSFC nodes and AlwaysOn replicas

Databases in the AG

user databases (no system databases)
read/write
multi-user
AUTO_CLOSE disabled
full recovery mode
not configured for database mirroring

Steps

The following steps need to be performed in this order:

Add Windows Failover Clustering (WSFC) to each replica (server)
Configure WSFC on your primary replica
Configure SQL Server on each replica
Configure Logins & Replicas
Install AlwaysOn

Sources:

https://www.sqlrx.com/steps-for-installing-sql-server-alwayson-availability-groups/

https://www.sqlservercentral.com/articles/steps-for-installing-alwayson-availability-groups-sql-2019

https://docs.microsoft.com/en-us/windows-server/failover-clustering/create-failover-cluster#validate-the-configuration

Restore an existing availability group database participating in SQL Server Always On Availability Groups

Tue, 07 Jun 2022 10:16:43 GMT

https://www.sqlshack.com/restore-an-existing-availability-group-database-participating-in-sql-server-always-on-availability-groups/

https://mlichtenberg.wordpress.com/2016/02/02/how-to-restore-a-database-in-a-sql-server-alwayson-availability-group/

Using the SQL Server Service Broker for Asynchronous Processing

Sat, 21 May 2022 10:33:52 GMT

https://www.sqlshack.com/using-the-sql-server-service-broker-for-asynchronous-processing/

Connection to SQL Server using SSL encryption

Sun, 27 Feb 2022 05:28:00 GMT

SSL connection encryption can be initiated either from the client, which can be an IIS website or Desktop application, or can be enforced at the server side. Either way, a certificate needs to be installed and available to the user or process establishing the connection that the other system can validate. Client side encryption is configured using "encrypt=true" or selecting a checkbox option on SQL Server Management Studio. Server side encryption for SQL Server is configured by adding a certificate and private key to the certificate store of the service account running the database engine and using SQL Server Configuration Manager to specify the certificate to use for encryption and set the Force Encryption property to true. It is recommended to use a certificate generated by your domain certificate authority or one purchased from a public CA because a self signed certificate is vulnerable to a man in the middle attack.

Source: https://stackoverflow.com/questions/37165653/connection-to-sql-server-using-ssl-encryption

Linked Tables from SQL Server to Microsoft Access

Sat, 18 Sep 2021 10:56:46 GMT

1) use file DSN (can be deleted after linked tables are created).

2) If using a trusted connection without a password being saved in Microsoft Access system tables, use the following template:

DRIVER=SQL Server Native Client 11.0
Regional=Yes
Encrypt=Yes
DATABASE=AdventureWorks
WSID=MyWorkstationName
APP=Microsoft Office
Trusted_Connection=Yes
SERVER=SQLServerHostName\SQLServerInstanceName
Description=Whatever Description You Like
TrustServerCertificate=Yes

Securing a Microsoft Access Database

Sun, 05 Sep 2021 15:30:00 GMT

https://www.techrepublic.com/blog/10-things/10-tips-for-securing-a-microsoft-access-database/

Access Front End to SQL Server Back End

Sun, 05 Sep 2021 11:32:43 GMT

https://social.msdn.microsoft.com/Forums/en-US/85757ab1-250e-460a-9e51-5a17516c5524/how-to-create-an-odbc-connection-for-runtime-access-to-sql-server-database-tables?forum=accessdev

https://support.microsoft.com/en-us/office/connect-access-to-sql-server-050d88f3-b2d6-4e76-b6f9-f3c556f139ea

https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14f

http://www.accessmvp.com/DJSteele/DSNLessLinks.html