Friday, March 9, 2012
Defining Alerts
Recently all our production databases were marked
as 'Suspect', anyway after a bit of work it was repaired.
However the only reason we found this out was the users
couldn't get in.
What I would like to do is define some alerts such
as 'database Production is not working', or replication is
no longer working.
I know where to do this, what I cannot find is background
information on what alert to raise (I have tried BOL on
Microsoft). Can anyone provide me background info, for
instance does alert 025 mean any error to a database which
stops it working ?
Thanks
J
Hi
Alert 025 is reased when a Error, with severity level 25 occurs.
You must check for error levels 20 and higher, those are very critcal.
The DB suspect error is Error 926, Severity Level 14
Regards
Mike
"Julie" wrote:
> Dear All,
> Recently all our production databases were marked
> as 'Suspect', anyway after a bit of work it was repaired.
> However the only reason we found this out was the users
> couldn't get in.
> What I would like to do is define some alerts such
> as 'database Production is not working', or replication is
> no longer working.
> I know where to do this, what I cannot find is background
> information on what alert to raise (I have tried BOL on
> Microsoft). Can anyone provide me background info, for
> instance does alert 025 mean any error to a database which
> stops it working ?
> Thanks
> J
>
|||Thanks Mike,
Is there any background information I can read up on ?
J
>--Original Message--
>Hi
>Alert 025 is reased when a Error, with severity level 25
occurs.
>You must check for error levels 20 and higher, those are
very critcal.[vbcol=seagreen]
>The DB suspect error is Error 926, Severity Level 14
>Regards
>Mike
>"Julie" wrote:
repaired.[vbcol=seagreen]
is[vbcol=seagreen]
background[vbcol=seagreen]
which
>.
>
|||Hi
http://msdn.microsoft.com/library/de...ar_cs_6x0l.asp
There is not much other infromation out there apart from what is in BOL.
Regards
Mike
"Julie" wrote:
> Thanks Mike,
> Is there any background information I can read up on ?
> J
>
> occurs.
> very critcal.
> repaired.
> is
> background
> which
>
|||Thanks Mike
>--Original Message--
>Hi
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_cs_6x0l.asp
>There is not much other infromation out there apart from
what is in BOL.[vbcol=seagreen]
>Regards
>Mike
>"Julie" wrote:
25[vbcol=seagreen]
are[vbcol=seagreen]
users[vbcol=seagreen]
replication[vbcol=seagreen]
on[vbcol=seagreen]
for
>.
>
Defining Alerts
Recently all our production databases were marked
as 'Suspect', anyway after a bit of work it was repaired.
However the only reason we found this out was the users
couldn't get in.
What I would like to do is define some alerts such
as 'database Production is not working', or replication is
no longer working.
I know where to do this, what I cannot find is background
information on what alert to raise (I have tried BOL on
Microsoft). Can anyone provide me background info, for
instance does alert 025 mean any error to a database which
stops it working ?
Thanks
JHi
Alert 025 is reased when a Error, with severity level 25 occurs.
You must check for error levels 20 and higher, those are very critcal.
The DB suspect error is Error 926, Severity Level 14
Regards
Mike
"Julie" wrote:
> Dear All,
> Recently all our production databases were marked
> as 'Suspect', anyway after a bit of work it was repaired.
> However the only reason we found this out was the users
> couldn't get in.
> What I would like to do is define some alerts such
> as 'database Production is not working', or replication is
> no longer working.
> I know where to do this, what I cannot find is background
> information on what alert to raise (I have tried BOL on
> Microsoft). Can anyone provide me background info, for
> instance does alert 025 mean any error to a database which
> stops it working ?
> Thanks
> J
>|||Thanks Mike,
Is there any background information I can read up on ?
J
>--Original Message--
>Hi
>Alert 025 is reased when a Error, with severity level 25
occurs.
>You must check for error levels 20 and higher, those are
very critcal.
>The DB suspect error is Error 926, Severity Level 14
>Regards
>Mike
>"Julie" wrote:
>> Dear All,
>> Recently all our production databases were marked
>> as 'Suspect', anyway after a bit of work it was
repaired.
>> However the only reason we found this out was the users
>> couldn't get in.
>> What I would like to do is define some alerts such
>> as 'database Production is not working', or replication
is
>> no longer working.
>> I know where to do this, what I cannot find is
background
>> information on what alert to raise (I have tried BOL on
>> Microsoft). Can anyone provide me background info, for
>> instance does alert 025 mean any error to a database
which
>> stops it working ?
>> Thanks
>> J
>.
>|||Hi
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_6x0l.asp
There is not much other infromation out there apart from what is in BOL.
Regards
Mike
"Julie" wrote:
> Thanks Mike,
> Is there any background information I can read up on ?
> J
>
> >--Original Message--
> >Hi
> >
> >Alert 025 is reased when a Error, with severity level 25
> occurs.
> >
> >You must check for error levels 20 and higher, those are
> very critcal.
> >
> >The DB suspect error is Error 926, Severity Level 14
> >
> >Regards
> >Mike
> >
> >"Julie" wrote:
> >
> >> Dear All,
> >> Recently all our production databases were marked
> >> as 'Suspect', anyway after a bit of work it was
> repaired.
> >> However the only reason we found this out was the users
> >> couldn't get in.
> >>
> >> What I would like to do is define some alerts such
> >> as 'database Production is not working', or replication
> is
> >> no longer working.
> >>
> >> I know where to do this, what I cannot find is
> background
> >> information on what alert to raise (I have tried BOL on
> >> Microsoft). Can anyone provide me background info, for
> >> instance does alert 025 mean any error to a database
> which
> >> stops it working ?
> >>
> >> Thanks
> >> J
> >>
> >.
> >
>|||Thanks Mike
>--Original Message--
>Hi
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_cs_6x0l.asp
>There is not much other infromation out there apart from
what is in BOL.
>Regards
>Mike
>"Julie" wrote:
>> Thanks Mike,
>> Is there any background information I can read up on ?
>> J
>>
>> >--Original Message--
>> >Hi
>> >
>> >Alert 025 is reased when a Error, with severity level
25
>> occurs.
>> >
>> >You must check for error levels 20 and higher, those
are
>> very critcal.
>> >
>> >The DB suspect error is Error 926, Severity Level 14
>> >
>> >Regards
>> >Mike
>> >
>> >"Julie" wrote:
>> >
>> >> Dear All,
>> >> Recently all our production databases were marked
>> >> as 'Suspect', anyway after a bit of work it was
>> repaired.
>> >> However the only reason we found this out was the
users
>> >> couldn't get in.
>> >>
>> >> What I would like to do is define some alerts such
>> >> as 'database Production is not working', or
replication
>> is
>> >> no longer working.
>> >>
>> >> I know where to do this, what I cannot find is
>> background
>> >> information on what alert to raise (I have tried BOL
on
>> >> Microsoft). Can anyone provide me background info,
for
>> >> instance does alert 025 mean any error to a database
>> which
>> >> stops it working ?
>> >>
>> >> Thanks
>> >> J
>> >>
>> >.
>> >
>.
>
Defining Alerts
Recently all our production databases were marked
as 'Suspect', anyway after a bit of work it was repaired.
However the only reason we found this out was the users
couldn't get in.
What I would like to do is define some alerts such
as 'database Production is not working', or replication is
no longer working.
I know where to do this, what I cannot find is background
information on what alert to raise (I have tried BOL on
Microsoft). Can anyone provide me background info, for
instance does alert 025 mean any error to a database which
stops it working ?
Thanks
JHi
Alert 025 is reased when a Error, with severity level 25 occurs.
You must check for error levels 20 and higher, those are very critcal.
The DB suspect error is Error 926, Severity Level 14
Regards
Mike
"Julie" wrote:
> Dear All,
> Recently all our production databases were marked
> as 'Suspect', anyway after a bit of work it was repaired.
> However the only reason we found this out was the users
> couldn't get in.
> What I would like to do is define some alerts such
> as 'database Production is not working', or replication is
> no longer working.
> I know where to do this, what I cannot find is background
> information on what alert to raise (I have tried BOL on
> Microsoft). Can anyone provide me background info, for
> instance does alert 025 mean any error to a database which
> stops it working ?
> Thanks
> J
>|||Thanks Mike,
Is there any background information I can read up on ?
J
>--Original Message--
>Hi
>Alert 025 is reased when a Error, with severity level 25
occurs.
>You must check for error levels 20 and higher, those are
very critcal.
>The DB suspect error is Error 926, Severity Level 14
>Regards
>Mike
>"Julie" wrote:
>
repaired.[vbcol=seagreen]
is[vbcol=seagreen]
background[vbcol=seagreen]
which[vbcol=seagreen]
>.
>|||Hi
http://msdn.microsoft.com/library/d...br />
6x0l.asp
There is not much other infromation out there apart from what is in BOL.
Regards
Mike
"Julie" wrote:
> Thanks Mike,
> Is there any background information I can read up on ?
> J
>
> occurs.
> very critcal.
> repaired.
> is
> background
> which
>|||Thanks Mike
>--Original Message--
>Hi
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_cs_6x0l.asp
>There is not much other infromation out there apart from
what is in BOL.
>Regards
>Mike
>"Julie" wrote:
>
25[vbcol=seagreen]
are[vbcol=seagreen]
users[vbcol=seagreen]
replication[vbcol=seagreen]
on[vbcol=seagreen]
for[vbcol=seagreen]
>.
>
Wednesday, March 7, 2012
Defining a boolean dimension attribute
You can create a named query in DSV to map the values on the fly.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Thanks for the response. I did think of that solution, but it has a problem for me. As an ISV, our product needs to be localizable, and embedding string translations in the DSV presents a localization problem.
When I do a query against a bit column using SQL Server Management Studio, it displays the contents as true/false, and in the DSV the column data type is displayed as "boolean". So it seems strange to me that SSAS can't do that string conversion automatically. Perhaps in a future release - I'll report an enhancement request for it.
I ended up solving the problem by snowflaking in a "BooleanValues" table which contains members (and corresponding names) for true and false.
|||For posterity, this looks like it's an actual bug in SSAS when using the managed SqlClient provider. When you switch the data source to use the SQL Native client, bit column values are translated to true/false automatically. I've reported it on Product Feedback.