Viewing 15 posts - 51,151 through 51,165 (of 59,098 total)
Thanks, guys... I appreciate the feedback...
Gus, did you test for rounding errors?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 9:45 am
T-SQL is absolutely NOT the place to format currency. This should be done in the GUI so that local currency formatting may be allowed to prevail. Also, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 6:58 am
There's a thousand posts on this... search for "Convert rows to columns".
Also, why do you want to do this? What if a Department has 1,000 employes? How would...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 6:32 am
You don't need XML for this... you can just do an INSERT with the understanding that there is no real good way to return the UniqueIdentifiers to the GUI without...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 6:30 am
You could use replication for this but I suspect you're trying to build a "Gold Set" or something similar one table at a time. You could use SELET/INTO which...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 6:24 am
Also, there's a City code that can get involved depending on the level of detail you want to show. For interational calls, the first 1-3 digits can be the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 6:13 am
Gail,
The country "Code" has to match the first 1 to 3 digits of either the ANI or the Dial_Digits. You wouldn't know that unless you've worked with Telephony Rating...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 6:09 am
jitendrapatil2006 (4/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 6:04 am
Yes... SQL Server Triggers are different than a lot of other RDBMS. In Oracle, for instance, you would do just as you have done except your would add "FOR...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 5:51 am
karthikeyan (4/11/2008)
which one is the efficient way ?
Ok... I admit it... I'm being a bit nasty... A "Senior Software Engineer" should know this. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2008 at 6:15 pm
Not true... you can use a TEXT datatype as a parameter.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2008 at 6:13 pm
LEN does not include trailing spaces... try the same thing with DATALENGTH.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2008 at 6:12 pm
I see what you posted and I'm still not sure what you want. Can you be a bit more descriptive, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2008 at 6:10 pm
Cool... if that's what you actually wanted.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2008 at 6:06 pm
The spit function works just fine and doesn't miss a thing. If, however, you don't have the data in the table to match, an INNER JOIN may give the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2008 at 6:05 pm
Viewing 15 posts - 51,151 through 51,165 (of 59,098 total)