Viewing 15 posts - 1,516 through 1,530 (of 7,191 total)
Thank you for responding
The original data consists of 6 tables.
The data from these are...
May 19, 2017 at 3:56 am
I don't really understand your requirement, but in trying to get to grips with it, I noticed that you have a denormalised design and the wrong data types. Parent_Group_ID should...
May 19, 2017 at 3:11 am
Nah, I've never smoked. But thanks for the offer!
I wasn't necessarily suggesting that you increase the scope of your alerting. I was just showing how you can reduce...
May 18, 2017 at 4:19 am
Please can I exchange it for a nice single malt?
The xp_readerrorlog proc takes up to two search parameters, so you can make your code more efficient, something like...
May 17, 2017 at 9:39 am
OK, so there are 16 different types of login failure message, and you have 36 instances of login failure messages in your errorlog. That makes sense to me. It sounds...
May 17, 2017 at 8:42 am
That's not what I mean. The table contains each possible message, but not each instance of when they were raised. As I understand it, if is_event_logged is 1, an entry...
May 17, 2017 at 5:36 am
I think it's to do with sys.messages, not SQL Server Agent alerts.
SELECT
m.message_id
, m.severity
, m.text FROM sys.messages m
JOIN sys.syslanguages l ON m.language_id =...
May 17, 2017 at 4:58 am
I'm not entirely sure, although I can see severity 14 and severity 18 errors in the errorlog of one of our servers.
Edit - take a look at the...
May 17, 2017 at 4:21 am
In the sample data you provided, there's a group for each distinct date and each distinct date is in its own group. Please post some more sample data illustrating a...
May 17, 2017 at 4:08 am
I think I'd just use xp_readerrorlog to pull all error details into a table, then poll that and alert accordingly.
John
May 17, 2017 at 3:30 am
May 17, 2017 at 2:33 am
Actually, I think you may need ALTER permission on the schema. Make sure you understand the dangers of doing this - explained here.
John
May 16, 2017 at 4:40 am
komal145 - Monday, May 15, 2017 9:15 AM.Can anyone tell me what is the error here.
SQL Server probably can. What is the...
May 15, 2017 at 9:22 am
This may be due to the new cardinality estimator (CE) that was introduced with SQL Server 2014. Is your database at compatibility level 130? Have a look at the (actual)...
May 15, 2017 at 9:20 am
Thanks Steve - I'll give it a try, in that case. I assume they must therefore convert dollars to pounds at point of sale. Having said that, it's not an...
May 15, 2017 at 8:44 am
Viewing 15 posts - 1,516 through 1,530 (of 7,191 total)