Viewing 15 posts - 26,101 through 26,115 (of 59,099 total)
mario17 (8/25/2013)
I just started to go into CROSS APPLY, being a JOIN person I'm trying to translate in into join, and still can't make it work as in original...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2013 at 11:19 am
Erland Sommarskog (8/25/2013)
Jeff Moden (8/24/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2013 at 11:02 am
johnabraham1980 (8/24/2013)
SELECT <non-pivoted column>,
[first pivoted column] AS <column name>,
[second pivoted column] AS <column name>,
.............................
FROM
(<SELECT query that produces the data>)
AS <alias for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2013 at 10:25 am
Heh... it's almost a shame that you figured it out on your own because, except for a couple of foreign key errors, you did such a nice job posting the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2013 at 9:55 am
We have to be a little careful here. The default for the setting at the database connection level is OFF and the default setting for connections within SSMS is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 9:25 pm
GilaMonster (8/24/2013)
Jeff Moden (8/24/2013)
the data isn't actually written as you would think until the transaction is committed.
In both cases the data changes are made to pages in memory and those...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 8:18 pm
If I were just starting out in this field today, I'd be asking the same questions. I was fortunate to be an "accidental DBA" starting back circa 1996 and...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 7:57 pm
@SQLFRNDZ (8/24/2013)
In addition,I was thinking of a load test resource bottlenecks before going to live with some software which can create the virtual users, For example...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 6:47 pm
dwain.c (8/23/2013)
Jeff Moden (8/23/2013)
Sean Lange (8/22/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 6:35 pm
Sean Lange (8/23/2013)
Jeff Moden (8/23/2013)
Sean Lange (8/22/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 6:34 pm
One of the other possible security problems is with the janitorial and repair staff. They have the keys and RFIDs to get just about anywhere. They might not...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 6:15 pm
I can't help with requirement #2 because I don't know what your data or table looks like and don't know what exactly you mean by "preferably the one with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 6:02 pm
shirish_padekar (8/24/2013)
Thanks, it worked! I am not sure about query performance, will check with actual database or may be will try other alternative as per your suggestion.
Thanks for the feedback....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 5:43 pm
One other thing that will help a bit. There's no need for the explicit transaction in the SP_GetNextValue sproc. It's just a waste of clock cycles because of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 5:17 pm
Where are you trying to "save off the SQL Error logs" to? A table or a file?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 5:03 pm
Viewing 15 posts - 26,101 through 26,115 (of 59,099 total)