Viewing 15 posts - 48,736 through 48,750 (of 59,099 total)
Loner (8/13/2008)
The one you posted for SQL Server 2000 worked liked...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 7:00 pm
You can get by without creating the extra temp table...
SELECT d.Name,t.N*10 AS DeciCount
FROM (SELECT Name,COUNT(*) AS TheCount
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:53 pm
Lian Pretorius (8/12/2008)
karthikeyan (8/12/2008)
Hey Trevor,I have tested the below script, It is giving perfect result.
Same here.
Trevor, Karthik's script above uses a temp table - Which cannot be used in view's...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:45 pm
It means "DataBase Owner" and is a server role. Lookup server roles in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:39 pm
sqlindia (8/12/2008)
Hi AllI want to list out columns name of SP into a table. They can be dynamic.
Thank in advance
sonny
I'm pretty sure this can't be done reliably. Sure,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:38 pm
I guess I'd have to ask... what does the CLR and the C# function do?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:17 pm
So far, the only place I've seen CLR's beat T-SQL is in the area of RegEx Replace...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:10 pm
Denby (7/21/2008)
Also, is the anything i should be monitoring from a DBA's perpective if feature is enable.
Absolutely! First, I'd make bloody sure that the source code was in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:09 pm
dolly (7/30/2008)
(i think so) i will solution for handling...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 6:01 pm
Without a whole lot more information ;), my answer would be... change it so it doesn't do that anymore. 🙂
You might want to conscribe any XML to the VARCHAR(MAX)...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 5:16 pm
It's a paradigm shift... with Cursors, you think "rows"... with setbased programming, you must learn to think "columns"... as in "What do I need to do to this column for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 5:12 pm
Lemme get this straight, Carl... you think it's better for the app to write and pass data in the forum of Unioned SELECT statements than to pass a comma seperated...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 5:04 pm
I'm thinking it could help employers notice me if they see who I've had forum discussions with.
Heh... WHICH forum discussions would you be talking about? You have precisely 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 4:20 pm
Which edition of SQL Server 2005 are you trying to install?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 4:12 pm
Venkatesan Prabu (8/17/2008)
insert into FirstTable values('Doc1','Attrib1','val1')
insert into FirstTable values('Doc2','Attrib2','val2')
insert into FirstTable values('Doc3','Attrib3','val3')
insert into FirstTable values('Doc4','Attrib4','val4')
select * from FirstTable
create table SecondTable(Attrib2 varchar(10),Attrib22 varchar(10))
insert into SecondTable...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 3:49 pm
Viewing 15 posts - 48,736 through 48,750 (of 59,099 total)