Viewing 15 posts - 42,841 through 42,855 (of 59,098 total)
chandrika5 (7/22/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 10:37 am
luckysql.kinda (7/22/2009)
Steve,Does it mean that when we rebuild the index for large DB as 1000GB, we should make the recovery model = SIMPLE
-LK
That might break your backup chain and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 10:21 am
tjm (7/22/2009)
Nope. Worked Great! Thanks for all your help!Implemented and is already on production server. 😀
-tjm
Wow... you folks don't waste any time. Thanks for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 10:19 am
Again... as a reminder... sp_OA* procs tend to be quite slow at things like this. If it turns out to be too slow, post back and I'll throw the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 8:28 am
tjm (7/22/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 8:26 am
jqd2001 (7/21/2009)
There are a lot of business rules regarding output that are difficult to express in T-SQL.
Unless it has to do with effecient RegEx, I've not known that to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 6:26 am
frecal (7/22/2009)
the query only really will indicate that the record has a relationship with another record in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 6:17 am
Thanks for the feedback... heh... wish I caught it before the first time I got burned by it. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 6:09 am
My humble apologies... looking back at this thread, I was wrong because I misread the intention. I allowed my fervor against having a CSV column in a table...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2009 at 6:05 am
The following method is a bit slow so far as I'm concerned, but it's also pretty safe. Let me know if you need something a whole lot faster with...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 10:40 pm
jqd2001 (7/21/2009)
The CLR Function, exec select statement, using datareader to iterate through, return result set in a table. The assembly marked SAFE.
Server is 64bit developer edition. We have a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 10:07 pm
frecal (7/20/2009)
I have Name table with...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 8:48 pm
I've never used PowerShell but I'm interested in it... anyone got an idea on this problem? Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 7:45 pm
You might also want to make that trigger an "Instead of" trigger so that not only are you capturing the information you want to catch the culprit, you're also preventing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 7:38 pm
Using code very similar to Dave's otherwise great example, try this...
create table #temp
(
Response varchar(500)
);
insert into #temp values(0)
insert into #temp values(1)
insert into #temp values(2)
insert into #temp values(10)
insert into #temp values(3)
insert into...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 7:32 pm
Viewing 15 posts - 42,841 through 42,855 (of 59,098 total)