Viewing 15 posts - 16 through 30 (of 40 total)
Yes, it is possible, but it's strange.
May 14, 2008 at 7:21 am
Thank you very much for your opinion.
Reporting system is our weakest point but we work on its improvement. It was much more worst several month ago and still there...
April 6, 2008 at 1:10 am
I live this forum but QoD makes me crazy too often...:crazy:
April 3, 2008 at 2:32 am
That's OK. As I said, I will use it only for warning user before potencially long waiting.
April 3, 2008 at 12:33 am
I know estimated plan. But how can I retrieve its information from an application?! I see that I can do i t in SSMS...
April 2, 2008 at 3:54 am
Yes, I know that. But is not useful for me beacuse I don't want to execute query.
We already use NOLOCK for queries used in our reports.
April 2, 2008 at 1:48 am
Could you tell us, where the problem was?
April 2, 2008 at 12:39 am
It will be quite complicated to parse EVENTDATA, but it is possible. Thank you, Andras!
February 29, 2008 at 8:12 am
Why to do this? ORDER BY should not be inside view and I think it is good that it is not supported by SQL 2005!
February 22, 2008 at 1:42 am
Not only triggers cause this error, the same problem is with nesting views...
January 9, 2008 at 2:19 am
I have noticed this error in nesting views. If you have for example 5 views (each of 8 tables) and you create view with joins to all of them, you...
January 9, 2008 at 2:17 am
I would answer to both question - possible blocking problem, out of date statistics or indexes
December 6, 2007 at 1:37 am
Sorry for mistake, it should be:
WITH CTE_Code(Code) AS
(
SELECT 21
UNION ALL
SELECT 66
UNION ALL
SELECT 34
UNION ALL
SELECT 36
UNION ALL
SELECT 37
UNION ALL
SELECT 35
UNION ALL
SELECT 33
UNION ALL
SELECT 38
UNION ALL
SELECT 39
UNION ALL
SELECT 112
UNION ALL
SELECT 121
)
SELECT...
December 6, 2007 at 12:59 am
Viewing 15 posts - 16 through 30 (of 40 total)