Viewing 15 posts - 46,396 through 46,410 (of 59,095 total)
Never mind... the answer is YES... you CAN use OPENROWSET in the view. What that means is that you CAN use a stored procedure as the source for a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2008 at 9:39 am
Ummmm.... Anyone know for sure if OPENROWSET, OPENQUERY, or OPENDATASOURCE can be used in a view or not? That could be the ticket.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2008 at 9:28 am
Ummmm... if the real tables are going to be in a database that doesn't have SIMPLE recovery, then probably not. If the temp tables are being used as replacements...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2008 at 9:19 am
ramadesai108 (12/26/2008)
I previsouly added the case statement in the group by, but forgot to add it in the order by and that's where the problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2008 at 9:06 am
Madhivanan (12/26/2008)
Refer
Yep... we all agree on that. I believe the main complaint is... the documentation doesn't say anything about the default size.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2008 at 8:47 am
Interesting concept... but it doesn't work correctly. I ran the code and the test code, as is... the results are not exactly a cross tab... look at the scores...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 1:19 pm
Perry Whittle (12/25/2008)
Lynn Pettis (12/17/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 12:12 pm
Heh... only 365 brain cell shopping days left...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 12:09 pm
Man, I sure hope they survive... I don't believe folks understand what an impact they've had on the United States and North America in general in the last 100 years....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 12:07 pm
Oh yeah... almost forgot... you need a Tally table for that code to work... please see the following...
The "Numbers" or "Tally" Table: What it is...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 11:57 am
Kit Brandner (12/22/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 11:52 am
Heh... there's an Auto Industry in Michigan??? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 9:50 am
I find both those things to be true with a lot of authors.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 9:47 am
You're supposed to ask for them BEFORE Christmas! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 9:41 am
YSLGuru (12/15/2008)
I think I may have come across a bug with the Replace() function in SQL Server 2005.
For what it's worth, I agree... if you compare the way the very...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2008 at 8:45 am
Viewing 15 posts - 46,396 through 46,410 (of 59,095 total)