Viewing 15 posts - 51,136 through 51,150 (of 59,091 total)
Greg... stupid question on my part, but have you tried using RTRIM to get rid of the trailing spaces?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 10:35 am
TheSQLGuru (4/14/2008)
On a side note, I personally despise views!! As a consultant they REALLY confound my efforts to examine/tune my client's queries!
Hear here! I second that... wasn't going...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 10:31 am
David.Mizelle (4/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 10:28 am
david.buncle (4/14/2008)
TEST? This datatype isn't recognised for SQL Server 2000... Did you mean TEXT?, if so this is invalid for a local variable.
... and, although you can't declare a local...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 10:24 am
david.buncle (4/14/2008)
TEST? This datatype isn't recognised for SQL Server 2000... Did you mean TEXT?, if so this is invalid for a local variable.
Yes... TEXT... coffee deprivation while typing. Thank...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 10:23 am
Derek Dongray (4/14/2008)
Both Jeff's and Peso's queries do not eliminate pairs where the status stays the same.
Sorry... with all the other stuff, I missed that requirement altogether.
Additionally, as Peso...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 10:22 am
I wonder which would work more quickly? I think the CLR might win this one because it uses implicit functions...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 9:54 am
GilaMonster (4/14/2008)
CREATE TRIGGER On_Delete
ON tblActivityArchive
AFTER DELETE
AS
BEGIN...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2008 at 9:49 am
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
Viewing 15 posts - 51,136 through 51,150 (of 59,091 total)