Viewing 15 posts - 46 through 60 (of 125 total)
You seem content on using CLR (like you were at the start of the thread), so let us know how it goes.
My 5 cents: If you're using CLR to hide...
February 22, 2011 at 10:34 am
February 21, 2011 at 6:03 am
Check your security options in your linked servers. Anonymous means just that: as far as SQL is concerned you're not passing credentials.
Carlton.
February 18, 2011 at 9:00 am
My train of thought is that NOLOCK is something to be used carefully...VERY carefully.
It can cause some unforeseen, extremely prickly issues.
One of which being trying to get NOLOCK out...
February 10, 2011 at 4:33 am
Correct: log shipping should be fine (not touching the primary DB).
But you should to look at why mirroring won't resume, check the SQL ERRORLOG, server event logs etc (on both...
February 10, 2011 at 4:15 am
This is a bit cruel, the @@error has been changed to black...
Carlton.
January 19, 2011 at 5:14 am
GilaMonster (1/5/2011)
Carlton Leach (1/5/2011)
Because you'll be looking to restore it if possible.Maybe. Depends on a number of factors.
Agreed, should have included the word 'generally' or 'probably'
January 5, 2011 at 6:24 am
Yep your DB has spat it.
As Gila said: have you got backups? (good ones). Because you'll be looking to restore it if possible.
also:
- what is the role of DB?...
January 5, 2011 at 5:47 am
If we want to talk about workarounds: how about threaten the halfwit who designed/built such a piece of cack and put you in a position where you had to deal...
January 5, 2011 at 5:16 am
- 32 or 64 bit?
- have you got lock pages in memory set?
- version of SQL?
Carlton.
January 5, 2011 at 4:57 am
At a guess: need to adjust your memory settings as per the kb mentioned.
Tricky thing to diagnose in some cases, but you may benefit from trying to trace what...
January 4, 2011 at 3:48 am
Sorry changed my reply as I didn't see the second page of comments
December 14, 2010 at 5:34 am
Viewing 15 posts - 46 through 60 (of 125 total)