October 6, 2016 at 1:06 pm
Lot of SQL dumps filling C:\ and they are continuous SQLDump####.mdmp and .txt. It SQL 2014 SP1. Any suggestion how to resolve this.
October 6, 2016 at 1:21 pm
psred (10/6/2016)
Lot of SQL dumps filling C:\ and they are continuous SQLDump####.mdmp and .txt. It SQL 2014 SP1. Any suggestion how to resolve this.
Read the text files, check the errorlog, work out what the problem is based on what you find.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 6, 2016 at 1:27 pm
Is listing a stored procedure in all the text files. But what could be the problem with stored proc.
October 6, 2016 at 1:40 pm
The sky is green and the grass is blue.
You haven't given us anything with which to even formulate an answer. We are not mind readers and definitely don't have access to your systems to be able to look for ourselves.
Post the errors (complete error messages) and we might be able to help you better.
October 6, 2016 at 1:48 pm
psred (10/6/2016)
Is listing a stored procedure in all the text files. But what could be the problem with stored proc.
You have been here long enough to realise that this is not enough information. Actually, it's barely any information.
If I listed 4,000 possible problems with your stored proc, ie every possible problem with any stored proc I have ever seen in my life, would that be helpful to you? Because that's as refined as I could be, given your posts.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply