Viewing 15 posts - 42,811 through 42,825 (of 59,063 total)
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
keerthy.vishweshwarachar (7/21/2009)
Great!!This is what I required...
Thanks
Ummm... be careful... try it with the value like '1e2'. Never use "IsNumeric" as an "IsAllDigits" function because it's not. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 6:42 pm
Heh... on the flip side, who cares? If you've got system with the latest sp and some of the hot fixes and it's been up and running for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 6:36 pm
It could be normal for the apps you're running or there might be a scheduled job that runs every 5 minutes or it could be replication or it could be....
The...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 6:30 pm
jay.jose (7/21/2009)
I'll be posting more problems as they arise ^_^
I recommend you study the article at the first link in my signature lines below before you do that. You'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 6:24 pm
sturner (7/21/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2009 at 6:20 pm
Viewing 15 posts - 42,811 through 42,825 (of 59,063 total)