New answers tagged

2

ANSI_DEFAULTS isn't really a distinct option, but a logical grouping of several other session-based options: IMPLICIT_TRANSACTIONS CURSOR_CLOSE_ON_COMMIT ANSI_WARNINGS ANSI_PADDING ANSI_NULLS QUOTED_IDENTIFIER ANSI_NULL_DFLT_ON You can use the @@OPTIONS configuration function to get the bit-masked value of the current Session settings, the values of ...


0

You will need to use DBCC USER Options to find..DBCC userOptions displays only values that are set.If you are not able to find any setting here,that means it is not set SET ANSI_DEFAULTS ON; GO -- Display the current settings. DBCC USEROPTIONS; GO -- SET ANSI_DEFAULTS OFF. SET ANSI_DEFAULTS OFF; GO ---Output: textsize 2147483647 ...


0

Below query is similar to what describe is doing. Only difference is it will also give you reference tables and reference columns for foreign keys. SET @row=0; SELECT @row:=@row + 1 AS ID, c.COLUMN_NAME AS 'Column Name', c.COLUMN_TYPE AS 'Column Type', c.IS_NULLABLE AS 'Is Null?', (CASE WHEN c....


2

This will always return a single row with NULL in all the columns of the table: SELECT t.* FROM (SELECT 1) AS dummy LEFT JOIN table_name AS t ON FALSE ; This will always return a single row with NULL in all the columns of the table if the table is empty and real data from one row if it isn't empty: SELECT t.* FROM (SELECT 1) AS dummy LEFT ...


0

Just want to answer the question I asked : To configure AOAGs with Synchronous mode + Automatic Failover -- This is possible only with Stand-Alone SQL Instances in SYNCHRONIZED state but not with SQL Server Failover Cluster Instances (Asynchronous) as the principle/point of Automatic Failover to AOAGs with FCI turns out to be a issue/conflict and not ...


1

This always happens because during setup you forgot to adjust your instance to be in both Windows and server authentication. Open SQL Server Management Studio; log in using Windows authentication; right click on your server then properties, then security tab, and mark on both Windows and server authentication; then click ok. Close SSMS then here is the ...



Top 50 recent answers are included