Can a burrito corrupt a single user's records?

I have a user of SQL-based CRM application. She is the only one who is
unable to see her associated contact records. She is also the only user on
the same electrical circuit as the kitchen at one of our offices. One day
someone was microwaving a frozen burrito and blew the circuit breaker. The
lights in the kitchen went out, the fridge and microwave stopped, and the PC
which had the application open, lost power. Has anyone else seen incidents
where power loss corrupts not an entire DB but an individual's records? Is
there a burrito brand that can prevent this from recurring (jk). Thanks,
Pancho.
The important question is, was this a plain burrito, or was there cheese
involved? Oh, and I should probably also ask, black beans or pintos?
While you're figuring out the answer to that one, run DBCC CHECKDB on your
database and see if you can repair the issues. There may be more corruption
you're not seeing simply because no one else has retrieved the rows -- yet.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
"Pancho" <Pancho@.discussions.microsoft.com> wrote in message
news:0E8A27CD-039E-4892-9F7D-1CF05F878269@.microsoft.com...
> I have a user of SQL-based CRM application. She is the only one who is
> unable to see her associated contact records. She is also the only user
on
> the same electrical circuit as the kitchen at one of our offices. One day
> someone was microwaving a frozen burrito and blew the circuit breaker.
The
> lights in the kitchen went out, the fridge and microwave stopped, and the
PC
> which had the application open, lost power. Has anyone else seen
incidents
> where power loss corrupts not an entire DB but an individual's records?
Is
> there a burrito brand that can prevent this from recurring (jk). Thanks,
> Pancho.
|||If the burrito is the culprit, I would like to suggest that it be called
Bandito Burrito... ;-)
"Pancho" <Pancho@.discussions.microsoft.com> wrote in message
news:0E8A27CD-039E-4892-9F7D-1CF05F878269@.microsoft.com...
>I have a user of SQL-based CRM application. She is the only one who is
> unable to see her associated contact records. She is also the only user
> on
> the same electrical circuit as the kitchen at one of our offices. One day
> someone was microwaving a frozen burrito and blew the circuit breaker.
> The
> lights in the kitchen went out, the fridge and microwave stopped, and the
> PC
> which had the application open, lost power. Has anyone else seen
> incidents
> where power loss corrupts not an entire DB but an individual's records?
> Is
> there a burrito brand that can prevent this from recurring (jk). Thanks,
> Pancho.
|||MSDN has covered this topic in depth:
http://msdn.microsoft.com/products/S...x?item=burrito
(ok, so I was having a little querystring fun... it's Friday, sue me.)
Pancho wrote:
>I have a user of SQL-based CRM application. She is the only one who is
>unable to see her associated contact records. She is also the only user on
>the same electrical circuit as the kitchen at one of our offices. One day
>someone was microwaving a frozen burrito and blew the circuit breaker. The
>lights in the kitchen went out, the fridge and microwave stopped, and the PC
>which had the application open, lost power. Has anyone else seen incidents
>where power loss corrupts not an entire DB but an individual's records? Is
>there a burrito brand that can prevent this from recurring (jk). Thanks,
>Pancho.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200508/1
|||Can u send that burrito ,me i want to test on my production database
with 200 users.
They all are hungry
thanx this helps u
from
killer
|||You got the path wrong:
http://msdn.microsoft.com/products/S...x?item=burrito
:D
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
"Frefaln via droptable.com" <forum@.droptable.com> wrote in message
news:52BE5071FF4C0@.droptable.com...
> MSDN has covered this topic in depth:
>
http://msdn.microsoft.com/products/S...x?item=burrito[vbcol=seagreen]
>
> (ok, so I was having a little querystring fun... it's Friday, sue me.)
>
> Pancho wrote:
on[vbcol=seagreen]
day[vbcol=seagreen]
The[vbcol=seagreen]
PC[vbcol=seagreen]
incidents[vbcol=seagreen]
Is
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200508/1
|||I like it when somebody add a little bit of humor to our everyday problems.
Adding to what Adam said, check if the property "TORN_PAGE_DETECTION" is on
in this db.
AMB
"Adam Machanic" wrote:

> The important question is, was this a plain burrito, or was there cheese
> involved? Oh, and I should probably also ask, black beans or pintos?
> While you're figuring out the answer to that one, run DBCC CHECKDB on your
> database and see if you can repair the issues. There may be more corruption
> you're not seeing simply because no one else has retrieved the rows -- yet.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
> "Pancho" <Pancho@.discussions.microsoft.com> wrote in message
> news:0E8A27CD-039E-4892-9F7D-1CF05F878269@.microsoft.com...
> on
> The
> PC
> incidents
> Is
>
>
|||Perhaps a variant of Montezuma's Revenge?
"ChrisR" wrote:

> If the burrito is the culprit, I would like to suggest that it be called
> Bandito Burrito... ;-)
>
> "Pancho" <Pancho@.discussions.microsoft.com> wrote in message
> news:0E8A27CD-039E-4892-9F7D-1CF05F878269@.microsoft.com...
>
>
|||Me too. But it really did happen!
"Frefaln via droptable.com" wrote:

> MSDN has covered this topic in depth:
> http://msdn.microsoft.com/products/S...x?item=burrito
>
> (ok, so I was having a little querystring fun... it's Friday, sue me.)
>
> Pancho wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200508/1
>
|||Adam:
1. Thanks for the DBCC suggestion.
2. Early reports are that it was beef, bean and cheese. It may have been
the Tina's brand which are cheap but good.
3. Our engineers are attempting a workaround by running the microwave in
"Thaw" mode first to soften the burrito, then zapping it at full power to
heat before eating, for a briefer time period.

"Adam Machanic" wrote:

> The important question is, was this a plain burrito, or was there cheese
> involved? Oh, and I should probably also ask, black beans or pintos?
> While you're figuring out the answer to that one, run DBCC CHECKDB on your
> database and see if you can repair the issues. There may be more corruption
> you're not seeing simply because no one else has retrieved the rows -- yet.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
> "Pancho" <Pancho@.discussions.microsoft.com> wrote in message
> news:0E8A27CD-039E-4892-9F7D-1CF05F878269@.microsoft.com...
> on
> The
> PC
> incidents
> Is
>
>