Hi ,

I have a very peculiar situation

I see a SELECT statement goes into roll back when killed on SQL Server 2014 always-on and it never rolls back.

It does have temp tables but should that cause infinite rollback ?

Only only option I am left with is to fail over and the re-sync the Db's 

I have a csv file that I need to bulk import using an xml format file . I cannot use SSIS since I will have hundreds of csv files all different and already have the table metadata . I figured should be simpler to script format files based on the table schema ex:

Csv file is

"column 1","column 2","column 3","column 4","column 5","column 6"

"John","Doe","fieldJohn","valJohn","2.45","1"

"Mary","Jay","fieldMary","valMary","2.45","1"

"Roger","Moore","fieldRoger","valRoger","2.45","1"

Can generate an xml format file from table running bcp however this will not handle the “ for the text qualifiers before and after every column value but just the comma, how do I add the “ text qualifier before and after in the xml format file? even worse the import is incorrect if there are commas inside the column value . I cannot change the source export.

Thank you,

<?xml version="1.0"?>

<BCPFORMAT xmlns="http://schemas.microsoft.com/sqlserver/2004/bulkload/format" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

 <RECORD>

  <FIELD ID="1" xsi:type="CharTerm" TERMINATOR="," MAX_LENGTH="500" COLLATION="Latin1_General_CI_AS"/>

  <FIELD ID="2" xsi:type="CharTerm" TERMINATOR="," MAX_LENGTH="500" COLLATION="Latin1_General_CI_AS"/>

  <FIELD ID="3" xsi:type="CharTerm" TERMINATOR="," MAX_LENGTH="500" COLLATION="Latin1_General_CI_AS"/>

  <FIELD ID="4" xsi:type="CharTerm" TERMINATOR="," MAX_LENGTH="500" COLLATION="Latin1_General_CI_AS"/>

  <FIELD ID="5" xsi:type="CharTerm" TERMINATOR="," MAX_LENGTH="500" COLLATION="Latin1_General_CI_AS"/>

  <FIELD ID="6" xsi:type="CharTerm" TERMINATOR="\r\n" MAX_LENGTH="500" COLLATION="Latin1_General_CI_AS"/>

 </RECORD>

 <ROW>

  <COLUMN SOURCE="1" NAME="column 1" xsi:type="SQLVARYCHAR"/>

  <COLUMN SOURCE="2" NAME="column 2" xsi:type="SQLVARYCHAR"/>

  <COLUMN SOURCE="3" NAME="column 3" xsi:type="SQLVARYCHAR"/>

  <COLUMN SOURCE="4" NAME="column 4" xsi:type="SQLVARYCHAR"/>

  <COLUMN SOURCE="5" NAME="column 5" xsi:type="SQLVARYCHAR"/>

  <COLUMN SOURCE="6" NAME="column 6" xsi:type="SQLVARYCHAR"/>

 </ROW>

</BCPFORMAT>

This is actually Windows Internal database in Windows 2016 server. I installed the feature and noticed that this error always shows up every time I restarted the database engine. The database instance will start fine and I can connect to the instance using SSMS. Why would the error show? This is just the feature install and has not other application connecting to the database engine yet.

Thanks

Hi

1) I have an instance of SQL server. I need to identify what port its listing on (so as to allow a firewall rule from another domain).

If I start up SSMS and execute SP_READERROR log, I can see entries that say:

I have an instance of SQL server. Its listening on the default port of 1433 

I need to setup a firewall rule from another domain (checkpoint firewall rule, not windows firewall)

In SQL config manager , if I right click on Sql server network configuration, Protocols { for the instance name), there is a force encryption setting - which can be set to Yes or No.

Ideally we would like connections coming from the 2nd domain via the firewall to be forced to use encryption, but leave existing clients on the same domain to not use encryption (as they currently do).

Is the force encryption setting global to the instance ? (it appears to be ) - or can it be done port by port ?

Are there any other options ?

Regards

G

Hello Folks,

I have a SQL having so many databases of our customers which is generating crash logs every 2 minutes. below is the error logs for your reference. can you please help me to resolve the issue.

18-09-19 09:36:33.28 spid438     00000002 Module(UNKNOWN+00000000)
2018-09-19 09:36:33.28 spid438     CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:36:33.28 spid438     Stack Signature for the dump is 0x61CCA0F7
2018-09-19 09:36:34.03 spid438     External dump process return code 0x20000001.
External dump process returned no errors.

2018-09-19 09:36:34.03 Server      Error: 17310, Severity: 20, State: 1.
2018-09-19 09:36:34.03 Server      A user request from the session with SPID 438 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
2018-09-19 09:39:06.31 spid121     CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:39:06.31 spid121     CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:39:06.31 spid121     ***Symbol load failed - Proceed to dump without any symbols
2018-09-19 09:39:06.31 spid121     ***Stack Dump being sent to c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0524.txt
2018-09-19 09:39:06.31 spid121     SqlDumpExceptionHandler: Process 121 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2018-09-19 09:39:06.31 spid121     * *******************************************************************************
2018-09-19 09:39:06.31 spid121     *
2018-09-19 09:39:06.31 spid121     * BEGIN STACK DUMP:
2018-09-19 09:39:06.31 spid121     *   09/19/18 09:39:06 spid 121
2018-09-19 09:39:06.31 spid121     *
2018-09-19 09:39:06.31 spid121     *
2018-09-19 09:39:06.31 spid121     *   Exception Address = 6FA232E6 Module(UNKNOWN+00000000)
2018-09-19 09:39:06.31 spid121     *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
2018-09-19 09:39:06.31 spid121     *   Access Violation occurred reading address 00000000
2018-09-19 09:39:06.31 spid121     * Input Buffer 74 bytes -
2018-09-19 09:39:06.31 spid121     *  SELECT TOP 1 * FROM AccountSynonymous
2018-09-19 09:39:06.31 spid121     *  
2018-09-19 09:39:06.31 spid121     *
2018-09-19 09:39:06.31 spid121     *  MODULE                          BASE      END       SIZE
2018-09-19 09:39:06.31 spid121     *
2018-09-19 09:39:06.31 spid121     *        Edi: E0403B44:  7430FFC8  7430FF20  8F850738  8F850708  00000000  74313A20  
2018-09-19 09:39:06.31 spid121     *        Esi: 00000000:  
2018-09-19 09:39:06.31 spid121     *        Eax: 00000000:  
2018-09-19 09:39:06.31 spid121     *        Ebx: 105F7F40:  00000000  00000000  00000000  00000000  00000000  00000000  
2018-09-19 09:39:06.31 spid121     *        Ecx: 105F7E8C:  00000000  00000000  00000000  00000000  00000000  00000000  
2018-09-19 09:39:06.31 spid121     *        Edx: E0403BFD:  00000000  00000000  A4000000  007430A2  00000000  00000000  
2018-09-19 09:39:06.31 spid121     *        Eip: 6FA232E6:  8B51068B  247489CE  0C50FF30  44C7C033  00001024  44C70000  
2018-09-19 09:39:06.31 spid121     *        Ebp: 105F7ED4:  E0402F08  6FA235B6  105F7F40  00000005  912BC8C0  00000100  
2018-09-19 09:39:06.31 spid121     *      SegCs: 00000023:  
2018-09-19 09:39:06.31 spid121     *     EFlags: 00010246:  
2018-09-19 09:39:06.31 spid121     *        Esp: 105F7E58:  105F7F38  8F85082C  E0403B44  105F7F40  00000000  00000010  
2018-09-19 09:39:06.31 spid121     *      SegSs: 0000002B:  
2018-09-19 09:39:06.31 spid121     * *******************************************************************************
2018-09-19 09:39:06.31 spid121     * -------------------------------------------------------------------------------
2018-09-19 09:39:06.31 spid121     * Short Stack Dump
2018-09-19 09:39:06.31 spid121     6FA232E6 Module(UNKNOWN+00000000)
2018-09-19 09:39:06.31 spid121     6FA235B6 Module(UNKNOWN+00000000)
2018-09-19 09:39:06.31 spid121     CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:39:06.31 spid121     Stack Signature for the dump is 0xB0E6507A
2018-09-19 09:39:07.09 spid121     External dump process return code 0x20000001.
External dump process returned no errors.

2018-09-19 09:39:07.09 Server      Error: 17310, Severity: 20, State: 1.
2018-09-19 09:39:07.09 Server      A user request from the session with SPID 121 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
2018-09-19 09:44:58.78 Logon       Error: 18456, Severity: 14, State: 38.
2018-09-19 09:44:58.78 Logon       Login failed for user 'ELLENHELLSTEN'. Reason: Failed to open the explicitly specified database 'ELLENHELLSTENGLOBALData'. [CLIENT: 192.168.200.10]
2018-09-19 09:44:58.83 Logon       Error: 18456, Severity: 14, State: 38.
2018-09-19 09:44:58.83 Logon       Login failed for user 'ELLENHELLSTEN'. Reason: Failed to open the explicitly specified database 'ELLENHELLSTENGLOBALData'. [CLIENT: 192.168.200.10]
2018-09-19 09:47:05.57 spid522     CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:47:05.59 spid522     CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:47:05.59 spid522     ***Symbol load failed - Proceed to dump without any symbols
2018-09-19 09:47:05.59 spid522     ***Stack Dump being sent to c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0525.txt
2018-09-19 09:47:05.59 spid522     SqlDumpExceptionHandler: Process 522 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2018-09-19 09:47:05.59 spid522     * *******************************************************************************
2018-09-19 09:47:05.59 spid522     *
2018-09-19 09:47:05.59 spid522     * BEGIN STACK DUMP:
2018-09-19 09:47:05.59 spid522     *   09/19/18 09:47:05 spid 522
2018-09-19 09:47:05.59 spid522     *
2018-09-19 09:47:05.59 spid522     *
2018-09-19 09:47:05.59 spid522     *   Exception Address = 6FA232E6 Module(UNKNOWN+00000000)
2018-09-19 09:47:05.59 spid522     *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
2018-09-19 09:47:05.59 spid522     *   Access Violation occurred reading address 00000000
2018-09-19 09:47:05.59 spid522     * Input Buffer 74 bytes -
2018-09-19 09:47:05.59 spid522     *  SELECT TOP 1 * FROM AccountSynonymous
2018-09-19 09:47:05.59 spid522     *  
2018-09-19 09:47:05.59 spid522     *
2018-09-19 09:47:05.59 spid522     *  MODULE                          BASE      END       SIZE
2018-09-19 09:47:05.59 spid522     *
2018-09-19 09:47:05.59 spid522     *        Edi: D440DB44:  7430FFC8  7430FF20  D4408738  D4408708  00000000  74313A20  
2018-09-19 09:47:05.59 spid522     *        Esi: 00000000:  
2018-09-19 09:47:05.59 spid522     *        Eax: 00000000:  
2018-09-19 09:47:05.59 spid522     *        Ebx: 014B7AC0:  00000000  00000000  00000000  00000000  00000000  00000000  
2018-09-19 09:47:05.59 spid522     *        Ecx: 014B7A0C:  00000000  00000000  00000000  00000000  00000000  00000000  
2018-09-19 09:47:05.59 spid522     *        Edx: D440DBFD:  00000000  00000000  A4000000  007430A2  00000000  78000000  
2018-09-19 09:47:05.59 spid522     *        Eip: 6FA232E6:  8B51068B  247489CE  0C50FF30  44C7C033  00001024  44C70000  
2018-09-19 09:47:05.59 spid522     *        Ebp: 014B7A54:  D440CF08  6FA235B6  014B7AC0  00000005  D43F28C0  00000100  
2018-09-19 09:47:05.59 spid522     *      SegCs: 00000023:  
2018-09-19 09:47:05.59 spid522     *     EFlags: 00010246:  
2018-09-19 09:47:05.59 spid522     *        Esp: 014B79D8:  014B7AB8  D440882C  D440DB44  014B7AC0  00000000  00000010  
2018-09-19 09:47:05.59 spid522     *      SegSs: 0000002B:  
2018-09-19 09:47:05.59 spid522     * *******************************************************************************
2018-09-19 09:47:05.59 spid522     * -------------------------------------------------------------------------------
2018-09-19 09:47:05.59 spid522     * Short Stack Dump
2018-09-19 09:47:05.59 spid522     6FA232E6 Module(UNKNOWN+00000000)
2018-09-19 09:47:05.59 spid522     6FA235B6 Module(UNKNOWN+00000000)
2018-09-19 09:47:05.59 spid522     CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:47:05.59 spid522     Stack Signature for the dump is 0xB0E6507A
2018-09-19 09:47:06.43 spid522     External dump process return code 0x20000001.
External dump process returned no errors.

2018-09-19 09:47:06.43 Server      Error: 17310, Severity: 20, State: 1.
2018-09-19 09:47:06.43 Server      A user request from the session with SPID 522 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
2018-09-19 09:49:38.72 spid86      CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:49:38.73 spid86      CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:49:38.73 spid86      ***Symbol load failed - Proceed to dump without any symbols
2018-09-19 09:49:38.73 spid86      ***Stack Dump being sent to c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0526.txt
2018-09-19 09:49:38.73 spid86      SqlDumpExceptionHandler: Process 86 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2018-09-19 09:49:38.73 spid86      * *******************************************************************************
2018-09-19 09:49:38.73 spid86      *
2018-09-19 09:49:38.73 spid86      * BEGIN STACK DUMP:
2018-09-19 09:49:38.73 spid86      *   09/19/18 09:49:38 spid 86
2018-09-19 09:49:38.73 spid86      *
2018-09-19 09:49:38.73 spid86      *
2018-09-19 09:49:38.73 spid86      *   Exception Address = 6FA232E6 Module(UNKNOWN+00000000)
2018-09-19 09:49:38.73 spid86      *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
2018-09-19 09:49:38.73 spid86      *   Access Violation occurred reading address 00000000
2018-09-19 09:49:38.73 spid86      * Input Buffer 74 bytes -
2018-09-19 09:49:38.73 spid86      *  SELECT TOP 1 * FROM AccountSynonymous
2018-09-19 09:49:38.73 spid86      *  
2018-09-19 09:49:38.73 spid86      *
2018-09-19 09:49:38.73 spid86      *  MODULE                          BASE      END       SIZE
2018-09-19 09:49:38.73 spid86      *
2018-09-19 09:49:38.73 spid86      *        Edi: A865DB44:  7430FFC8  7430FF20  561C8738  561C8708  00000000  74313A20  
2018-09-19 09:49:38.73 spid86      *        Esi: 00000000:  
2018-09-19 09:49:38.73 spid86      *        Eax: 00000000:  
2018-09-19 09:49:38.73 spid86      *        Ebx: 004A79E0:  00000000  00000000  00000000  00000000  00000000  00000000  
2018-09-19 09:49:38.73 spid86      *        Ecx: 004A792C:  00000000  00000000  00000000  00000000  00000000  00000000  
2018-09-19 09:49:38.73 spid86      *        Edx: A865DBFD:  00000000  00000000  A4000000  007430A2  00000000  00000000  
2018-09-19 09:49:38.73 spid86      *        Eip: 6FA232E6:  8B51068B  247489CE  0C50FF30  44C7C033  00001024  44C70000  
2018-09-19 09:49:38.73 spid86      *        Ebp: 004A7974:  A865CF08  6FA235B6  004A79E0  00000005  9FEB68C0  00000100  
2018-09-19 09:49:38.73 spid86      *      SegCs: 00000023:  
2018-09-19 09:49:38.73 spid86      *     EFlags: 00010246:  
2018-09-19 09:49:38.73 spid86      *        Esp: 004A78F8:  004A79D8  561C882C  A865DB44  004A79E0  00000000  00000010  
2018-09-19 09:49:38.73 spid86      *      SegSs: 0000002B:  
2018-09-19 09:49:38.73 spid86      * *******************************************************************************
2018-09-19 09:49:38.73 spid86      * -------------------------------------------------------------------------------
2018-09-19 09:49:38.73 spid86      * Short Stack Dump
2018-09-19 09:49:38.73 spid86      6FA232E6 Module(UNKNOWN+00000000)
2018-09-19 09:49:38.73 spid86      6FA235B6 Module(UNKNOWN+00000000)
2018-09-19 09:49:38.73 spid86      CImageHelper::Init () Failed load of symbol file with path = C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\Binn\;c:\Program Files (x86)\Microsoft SQL Server\MSSQL12.HL\MSSQL\BINN - Not enough storage is available to process this command.

2018-09-19 09:49:38.73 spid86      Stack Signature for the dump is 0xB0E6507A
2018-09-19 09:49:39.55 spid86      External dump process return code 0x20000001.
External dump process returned no errors.

2018-09-19 09:49:39.56 Server      Error: 17310, Severity: 20, State: 1.
2018-09-19 09:49:39.56 Server      A user request from the session with SPID 86 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

Regards,

Mahi_nix

I am setting  up 2 Windows Server 2012 R2 x64 servers that I am installing a Cluster that will run instances of SQL 2008R2, SQL 2012, SQL 2014 and SQL 2016.  I have no issue with the SQL 2008, 2012 or 2014 installations.  I am having issues with the SQL 2016 instance mainly the agent will not start.  Now, before I start getting referenced to a whole bunch of links for various things, to let you know, I tried them all.  The ODBC 13.1 driver update does not have a x64 version, or at least none that I found.  SQL Server is starting up all the way, at least as far as I can see.  I am running both the SQL engine and the agent under a domain service account that I gave admins right to for the server as well as sysadmin rights for SQL.  I did do a repair with no luck and I am seeing this on both servers of the cluster.  I gave full rights to the service user to the folder C:\Windows\system32\LogFiles\Sum\.  The firewall is turned off for domain and private networks.  Yes, it is joined to the domain.  I am not using any custom ports, just out of the box.  Under the Agent properties I did set the local host server to the cluster name.

This is from the agent log:

? [100] Microsoft SQLServerAgent version 13.0.4001.0 (X64 unicode retail build) : Process ID 7528
? [495] The SQL Server Agent startup service account is domain\srv.user.
! [150] SQL Server does not accept the connection (error: 65535). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
! [000] Unable to connect to server 'CLS2016\SQL2016'; SQLServerAgent cannot start
! [298] SQLServer Error: 65535, SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
! [298] SQLServer Error: 65535, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
! [382] Logon to server 'CLS2016\SQL2016' failed (DisableAgentXPs)
? [098] SQLServerAgent terminated (normally)

I do have another install of SQL 2016 on a Server 2012 R2 but it is stand alone instance, no cluster no other SQL versions installed.  It does not have any issues

Thanks

Hi All,

I have a small query. I have a Server where we run all our job for clients. due to some internal constraints now we need to kick of a job on different server(server b) as part of the job on server(server a).

I need to wait for results(the job to complete on server b) before i go to next step in server a.

Is this possible?

Thanks & Regards,
Manjunath C Bhat,
http://manjunathcbhat.blogspot.com
http://manjunathcbhat.wordpress.com

Hi All,

I'm looking for a way to find out number of times my Archive DB is getting hit through view.

Here is the scenario. I have a view created with union all like below

Create View Myview
AS
Select ColumnA, ColumnB From ActiveDB..XYZ
UNION ALL
Select ColumnA, ColumnB From ArchiveDB..XYZ 

ActiveDB..XYZ table has 1 Year of Data

ArchiveDB..XYZ is having older than 1 Year Data.

If my user tried to access the old data which is older than 1 Year through view. Is there any way can we say that data accessed from Archive Database and how many times the archived is hit?

Greetings.  I want to create a Linked Server on my SQL Server 12.0.5207.0 that will allow me to query an Amazon Web Services Redshift database (Postrgres 8.2) directly from SSMS.  I have gotten to the point of successful connectivity testing from the linked server to AWS, but I am not able to run any queries.  Here are the steps I have taken so far.

I followed AWS's instructions; installing their 64-bit ODBC Driver on my 64-bit Windows Server 2012 R2 Datacenter and creating a System DSN via the 64-bit ODBC Administrator.  (https://docs.aws.amazon.com/redshift/latest/mgmt/install-odbc-driver-windows.html).  Under "Additional Configuration" of the System DSN, "Retrieve Entire Result Into Memory" is selected by default.  Under "Data Type Options" of the System DSN, "Use Unicode", Show Boolean Column as String", and "Text as LongVarChar" are all checked by default.  Also, "Max Varchar" is defaulted to '255', "Max LongVarChar" is defaulted to '8190', and "Max Bytea" is defaulted to 255.

For the MSDASQL Provider Properties, on the General Page, only the "Allow inprocess" option is checked.  All other options are unchecked.

I created a Linked Server with the following configuration;

• General Page, Provider = "Microsoft OLE DB Provider for ODBC Drivers"
• General Page, Product Name = "Amazon Redshift (x64)"
• General Page, Data Source = (my System DSN from above)
• General Page, Provider String = (blank)
• General Page, Location = (blank)
• General Page, Catalog = (blank)
• Security Page, "Be made using this security context" (and my AWS login and password)
• Server Options Page, Collation Compatible = "False"
• Server Options Page, Data Access = "True"
• Server Options Page, RPC = "True"
• Server Options Page, RPC Out = "True"
• Server Options Page, Use Remote Collation = "True"
• Server Options Page, Collation Name = (blank)
• Server Options Page, Connection Timeout = "0"
• Server Options Page, Query Timeout = "0"
• Server Options Page, Distributor = "False"
• Server Options Page, Publisher = "False"
• Server Options Page, Subscriber = "False"
• Server Options Page, Lazy Schema Validation = "False"
• Server Options Page, Enable Promotion of Distributed Transactions for RPC = "True"

Testing the System DSN connection through the ODBC Administrator is successful.

Testing the Linked Server connection through the right-click context menu is successful.

I can see the Redshift database, tables, and views listed under the Linked Server in the SSMS schema browser.

When I try to execute a simple select statement on one of the views in Redshift, using the 4-part naming convention, I get the following error;

OLE DB provider "MSDASQL" for linked server "REDSHIFT" returned message "Unspecified error".
OLE DB provider "MSDASQL" for linked server "REDSHIFT" returned message "[Amazon][Support] (40470) Conversion error at column 16 and row 1: Numeric value out of range.".
Msg 7311, Level 16, State 2, Line 25
Cannot obtain the schema rowset "DBSCHEMA_COLUMNS" for OLE DB provider "MSDASQL" for linked server "REDSHIFT". The provider supports the interface, but returns a failure code when it is used.

I also tried using the right-click menus on a view to "Script view as", "Select to", "new query editor menu", and I get a similar error;

I have a server with 8 physical sockets and 12 cores each.

when sql server startup , it use Automatic soft-NUMA to help me divided into 16 numanodes and each has 6 schedulers

from https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option?view=sql-server-2017

It mention 

Server with multiple NUMA nodes Less than 8 logical processors per NUMA node   Keep MAXDOP at or below # of logical processors per NUMA node
 Server with multiple NUMA nodes Greater than 8 logical processors per NUMA node  Keep MAXDOP at 8

so in my case. is it choosing 6 for maxdop ?

Hi,

I am using Window server 2012 R2 with SQL 2016. when I try to connect to SSIS using Management Studio its gives me error. when I write click on Management studio icon and run as administrator then it let me connect to SSIS using same window ID. how I can fix this issue

Hi All,

SQL SERVER 2014 running with latest CU, I am seeing "All" stolen memory coming from NUMA Node 001 because of that I am seeing more "Database Pages" on NUMA Node 0 and less on other.

Due to this I am seeing frequent PLE issue and Lazy Writer also working aggressively on NUMA 001.

Interestingly “Stolen Server Memory(KB)” at “Memory Manager” level showing “85,493,393” KB however “Stolen Memory Node (KB)” counter at Memory Node level showing “281,116,488” value.

Server have two NUMA NODE and SQL SERVER using affinity mask where in it is using 20 logical processors from each NUMA node.

Anyone seen this behavior in past? Expected? Anyway to balance the memory allocation for "Stolen Memory" or non-database pages ? I am suspecting this due to affinity mark but not sure. 

Thanks for your help.

Regards,

Vikas Rana

Environment: SQL Server 2014 on Windows Server 2012 R2.

Our application uses hibernate and the jTDS JDBC driver, so we are (by default) getting generated SQL statements coming through as sp_prepare and sp_execute.  Sometimes, I am able to find the prepared queries in the cache, but sometimes I'm not.  By cache, I mean sys.dm_exec_query_stats and sys._dm_exec_cached_plans.  What's strange is that even if they seem to be gone from the cache, the prepared statements execute successfully.  I'm wondering if there is some other location where I could consistently see/find the prepared statements, hopefully by their integer handle?

Thank you,

-Peter

I set up an extended events session collecting the blocked process report.

Unfortunately I found that the <inputbuf> element in the XML report is truncated in the blocked/blocking process elements.

Is there a way to circumvent this truncation?

Thanks in advance

Hi All,

Can you kindly confirm whether we  need to install Outlook Client on database server to configure SQL server database mail functionality in SQL server 2016 . 

Best Regards,
Sandy