Hi All, 

I am trying to connect Jira service desk on one windows server (svrap01) to a database on a named instance of MS SQL Server on another windows server (svrdb01) and am getting the error

Error connecting to database

The TCP/IP connection to the host SVRDB01, port 1433 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

I think the issue is that the named instance of the SQL Server on SVRDB01 is not listening on the right port.  How do I check/change which port the named instance is listening on?

Thanks for any help, Roscoe 

Here actually are 2 questions.

1. After a SQL Job finish on server 1 I want to trigger a SQL Job on Server 2.

Is there any typical solutions from Microsoft?

2. what are some popular ways to start a SQL job on different server.

Dear Experts,

How to fix CXPACKET waittype

Kiran

I am trying to access a blob on a network share but keep getting 

Msg 4861, Level 16, State 1, Line 3
Cannot bulk load because the file "\\server\share\1.jpg" could not be opened. Operating system error code 5(failed to retrieve text for this error. Reason: 15105).

the command is: 

select * from openrowset ( 
           bulk '\\server\share\1.jpg' 
           ,SINGLE_BLOB) x 

I can access the file from windows. I have given permissions to the share for the domain user running sqlserver 

obviously a delegation error. can a username/password be specified in the sp or openrowset? I just want access through sqlserver. I dont care how. would an assembly bypass this ? 

thanx

???

Trying to import data from Excel is giving this message.

Office365 64-bit

Here's what I tried:

1) I installed the 64-bit Access database engine 2016

2) I tried the 2010 & 2007 versions as well

3) I reinstalled Office365

I'm out of ideas. What else could be going on here?

This is the error:

Server log:

Date10/8/2019 1:21:21 AM
LogSQL Server (Archive #1 - 10/8/2019 7:09:00 AM)

SourceServer

Message
New queries assigned to process on Node 1 have not been picked up by a worker thread in the last 300 seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: 24%. System Idle: 67%.

This is the text file

Current time is 01:21:02 10/08/19.                                                                              
=====================================================================                                            
       BugCheck Dump                                                                                            
=====================================================================                                            

This file is generated by Microsoft SQL Server                                                                  
version 11.0.7462.6                                                                                             
upon detection of fatal unexpected error. Please return this file,                                               
the query or program that produced the bugcheck, the database and                                                
the error log, and any other pertinent information with a Service Request.                                       


Computer type is Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz.                                                       
Bios Version is HP     - 2                                                                                      
8 X64 level 8664, 3 Mhz processor (s).                                                                          
Windows NT 6.2 Build 9200 CSD .                                                                                 

Memory                               
MemoryLoad = 53%                     
Total Physical = 131037 MB           
Available Physical = 60906 MB        
Total Page File = 150402 MB          
Available Page File = 78606 MB       
Total Virtual = 134217727 MB         
Available Virtual = 134098520 MB     
**Dump thread - spid = 0, EC = 0x0000000000000000                                                               
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.SQL\MSSQL\LOG\SQLDump0005.txt          
* *******************************************************************************                                
*                                                                                                               
* BEGIN STACK DUMP:                                                                                             
*   10/08/19 01:21:02 spid 11568                                                                                
*                                                                                                               
* Deadlocked Schedulers                                                                                         
*                                                                                                               
* *******************************************************************************                                
* -------------------------------------------------------------------------------                                
* Short Stack Dump                   

Hi,

we are going to migrate SQL 2016 Enterprises to SQL 2017 Standard edition.

 what are the things to take care for this?

•   Compatibility?
•   can we upgrade SQL 2016 Ent to SQL 2017 Stand directly ( In-place upgrade)
•   we are using Rebuild with online /Table partition features in Enterprises. (what are the features differentiate with         standard)
•   Is there any difference in  Performance compare with SQL 2016 Ent vs SQL 2017Std.
• we configured Transnational Replication.

Hi,

We are using SQL Server Enterprise Evaluation 2016 (13.0.1601.5) with min memory 0 MB and Max Memory as default i.e. 2,147,483,647 MB. The RAM size is 32 GB. After restart (Failover Active to Passive and vice versa) of SQL Cluster Service, sqlservr.exe memory increases slowly i.e.  on first day 5 GB then next it reaches to 10 GB then next day 15 GB. Since memory keeps on increasing after 3-4 days  few SQL quries also takes very long time to execute. But if SQL service are restarted then those sql quries are executed within few seconds. After executing DBCC DROPCLEANBUFFERS and Freeproccache the memory is not released by SQL server. 

Also suppose If I set max memory to 15 GB then whether my daily running transactions (insert, update, select) will get fail or not after 3-4 days from restart of SQL services .

Requesting you to please suggest on this. 

Thanks in advance

Regards,

Nikhil P Desai

Is it normal for SQL Server to do a CHECKDB on a snapshot after the snapshot was created ? 

There is a powershell script at my customer site that runs snapshots each hour and today i see in the error log that its doing CHECKDB for 2 snapshots .. the CHECKDB finishes without errors. 

but why it doesnt run a checkdb for all? or why it starts to do a checkdb for these 2 snapshots this afternoon ? 

ilikefondue

Hi everyone,

Please let me know, can i configure always on in 2014 developer edition?

TITLE: Microsoft SQL Server Management Studio
------------------------------
Service 'Microsoft.SqlServer.Management.IRegistrationService' not found (Microsoft.SqlServer.Management.SDK.SqlStudio)
------------------------------
BUTTONS:

OK
------------------------------

Please tell me how can i fix this

Sajid

Hello Team,

I need to comission Database with Polybase feature enabled. The data size will be around 3 TB.

Can you suggest minimum s/w requirements like RAM , Processer etc etc.

Regards,

Error: 17311, Severity: 16, State: 1.

SQL Server 2012 on OS 2012

The port number of Analysis Services was changed to the same number as the SQL Server Engine and SQL Server Agent.  This was done by someone else and not me.  What happened was that the SQL Server Engine and Agent stopped.  I altered the port number for the SQL Server Engine and I got it working.  But I cannot start SQL Server Agent.  When I look at the log I get the following:

2014-09-25 15:37:37 - ? [100] Microsoft SQLServerAgent version 11.0.3431.0 (X64 unicode retail build) : Process ID 5172
2014-09-25 15:37:37 - ? [495] The SQL Server Agent startup service account is NT Service\SQLAgent$InstanceNameHere.
2014-09-25 15:37:37 - ! [150] SQL Server does not accept the connection (error: 64). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2014-09-25 15:37:37 - ! [000] Unable to connect to server 'ServerNameHere\InstanceNameHere'; SQLServerAgent cannot start
2014-09-25 15:37:37 - ! [298] SQLServer Error: 26, Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server. [SQLSTATE 08001]
2014-09-25 15:37:37 - ! [298] SQLServer Error: 64, TCP Provider: The specified network name is no longer available. [SQLSTATE 08001]
2014-09-25 15:37:37 - ! [298] SQLServer Error: 26, Client unable to establish connection [SQLSTATE 08001]
2014-09-25 15:37:37 - ! [298] SQLServer Error: 64, Client unable to establish connection due to prelogin failure [SQLSTATE 08001]
2014-09-25 15:37:37 - ! [382] Logon to server 'ServerNameHere\InstanceNameHere' failed (DisableAgentXPs)
2014-09-25 15:37:37 - ? [098] SQLServerAgent terminated (normally)

I have looked at various solutions and they don't seem to fix it.  Can anyone point me in the right direction?

lcerni

Hi All,

We were receiving many tickets saying sql reporting service was down yesterday.

Its reported that the sql reporting service was automatically restarting for sometime yesterday.

We see a msg 'Service started successfully' with event id: 0 intermittently for 2 hours. There were no logs that the service got stopped. We have only logs saying the service started successfully.

We dont see any errors except the below in eventvwr when the reporting service was restarted:

(Application error)
Faulting application name: SQLPS.exe, version: 12.0.2000.8, time stamp: 0x5306bda0
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19358, time stamp: 0x5ccfa112

(.Net Runtime error)
Application: SQLPS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException

Could you please help me in understanding the cause?

Hi, 
As part of performances story, we have made batch inserts instead of single inserts in our java code.

Please find Sample code code:

String myConnectionString ="jdbc:sqlserver://mbaastest18.konylabs.net:1433;databasename=TOMCATmfreportsdbSINGLEX56";try(Connection con =DriverManager.getConnection(myConnectionString,"root","whatever")){try(PreparedStatement ps = con.prepareStatement("INSERT INTO jdbc (`name`) VALUES (?)")){for(int i =1; i <=5; i++){
            ps.setString(1,String.format("Line %d: Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.",
                    i));
            ps.addBatch();}
        ps.executeBatch();}}

But the real problem is insertion is happening like below

INSERT INTO jdbc (`name`) VALUES ('Line 1: Lorem ipsum ...')
INSERT INTO jdbc (`name`) VALUES ('Line 2: Lorem ipsum ...')

But I need something like below. So, I tried attaching rewritebatchedstatements parameter to the connection url,it worked for mysql but not working sql server.

INSERTINTO jdbc (`name`)VALUES('Line 1: Lorem ipsum ...'),('Line 2: Lorem ipsum ...')

Is there any way to make it work?

I have read about bulk copy command, but currently we cannot afford to use it.
Any help would be appreciated. 

Hello,

We have an in-house developed database application that uses SQL Server 2016 (13.0.5101.9) for backend data storage. Numerous tables have identity columns configured as the key field. This week two of these identity columns randomly changed to substantially lower numbers. 

In one case the identity column changed from 20200954 to 20160296. In the other case the identity column changed from 20200000 to 20120046. In both cases the identity column was configured as an INT value with an increment step of 1. 

We had previously encountered the better known issue where identity values can skip by 1000 during a server restart. We took the prescribed measures to eliminate this.

Anyhow, in approximately ten years of use of this application (using two or three versions of SQL Server over this time), I don’t ever recall experiencing identity values randomly regressing to a lower value. I am wondering…

1.)   If anyone else has experienced this?

2.)   Is this a known issue?

3.)   Is there a known remedy?

It’s very unsettling having identity values randomly change.

Thank You,

Dale

Hi Experts,

Our database is going to suspect mode after SQL is getting restarted.

Further scrutinizing, we could see surplus space in OLTP In-memory filegroup.So kindly help to check on the issue based on below logs.

Failed to create new file 'K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\{0A5F80AB-2DB8-421E-AB01-C9EC2ED1F215}.hkckp'. Error code: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\stgutil.cpp : 171)
[WARNING] Database ID: [6]. Container ID: [{B63A9CA0-1367-4348-A464-6F7254D786F4}]. Container Path: [K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\]. Failed to allocate free file in container, will try again later. Error: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\freefilemgr.cpp : 725)
   [WARNING] Database ID: [6]. Failed to create new file 'K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\{3E9AB42B-2830-469F-8E3F-3FAA3AB7606D}.hkckp'. Error code: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\stgutil.cpp : 171)
[WARNING] Database ID: [6]. Container ID: [{B63A9CA0-1367-4348-A464-6F7254D786F4}]. Container Path: [K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\]. Failed to allocate free file in container, will try again later. Error: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\freefilemgr.cpp : 725)
  [WARNING] Database ID: [6]. Failed to create new file 'K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\{F45E0049-CB14-4286-BC31-D5678D81601E}.hkckp'. Error code: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\stgutil.cpp : 171)
  [WARNING] Database ID: [6]. Container ID: [{B63A9CA0-1367-4348-A464-6F7254D786F4}]. Container Path: [K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\]. Failed to allocate free file in container, will try again later. Error: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\freefilemgr.cpp : 725)
[WARNING] Database ID: [6]. Failed to create new file 'K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\{50E2314D-4916-46D2-BF5E-2034CC484F3D}.hkckp'. Error code: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\stgutil.cpp : 171)
  [WARNING] Database ID: [6]. Container ID: [{B63A9CA0-1367-4348-A464-6F7254D786F4}]. Container Path: [K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\]. Failed to allocate free file in container, will try again later. Error: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\freefilemgr.cpp : 725)
  [WARNING] Database ID: [6]. Failed to create new file 'K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\{031AEB33-4670-4B73-A644-16545EB9C794}.hkckp'. Error code: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\stgutil.cpp : 171)
 [WARNING] Database ID: [6]. Container ID: [{B63A9CA0-1367-4348-A464-6F7254D786F4}]. Container Path: [K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\]. Failed to allocate free file in container, will try again later. Error: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\freefilemgr.cpp : 725)
  [WARNING] Database ID: [6]. Failed to create new file 'K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\{AB62B3CF-C4EF-4BC5-A949-4BDF8D6A3D8D}.hkckp'. Error code: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\stgutil.cpp : 171)
 [WARNING] Database ID: [6]. Container ID: [{B63A9CA0-1367-4348-A464-6F7254D786F4}]. Container Path: [K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\]. Failed to allocate free file in container, will try again later. Error: 0x88000028. (e:\b\s3\sources\sql\ntdbms\hekaton\stglib\freefilemgr.cpp : 725)
[INFO] Database ID: [6]. Failed to open/create file of type '2' in container 'K:\MSSQL13.MSSQLSERVER\MSSQL\Data\XXXXXX_mod_dir\$HKv2\'. Error code: 0x88000028. Retrying the operation (1).

So kindly do check and let us know if you need any more information on this matter.Thank you

Regards,

Naren poosa

Can "Suspect" msdb be successfully repaired if there is no backup of the database?

Can you please send me the process that I should follow to repair the database?