Viewing 15 posts - 50,251 through 50,265 (of 59,091 total)
Sure... Barry is on the right track. Try that.
I guess I don't need to tell you that the column information stored in the NTEXT column should really be normalized...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 9:30 pm
It could be something as simple as a really lousy conference phone.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 9:21 pm
I gotta ask... why is the data stored this way? It's mostly "death by SQL" and now you want to compound the problem by converting it to the equivelent...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 9:18 pm
Think about it... the skinny table is an "EAV" (Entity, Attribute, Value)... a cross tab Select is all that is needed as the source of the update. Would be...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 9:14 pm
You're right... not enough sleep...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 8:41 pm
achaudhr (5/12/2008)
One example of the query I am using on the view is:
select BibNumber from [vw_TypesOnlinePeriodicalsJoin]
where TiQueryValue...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 7:59 pm
Thanks for the feedback... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 7:43 pm
There are exceptions, especially amongst friends. But some of these folks' arrogance is just beyond me... like I said, it must just be a difference in language because some...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 7:03 pm
No indexes on TableB?
What does your query look like?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 6:46 pm
Deleting lacs of duplicates is going to take a long time if you have indexes and triggers and maybe even indexed views...
How big is the table including the duplicates (in...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 6:44 pm
First, create a Tally table... see the following URL for what it is and how it replaces some loops... take time to read it 'cause it's worth it 😉
http://www.sqlservercentral.com/articles/TSQL/62867/
Next,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 6:10 pm
Thanks for the "plug", Matt! 🙂
The article Matt speaks of is at the following URL...
http://www.sqlservercentral.com/articles/T-SQL/63003/
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 5:45 pm
Anirban Paul (5/21/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 5:36 pm
Implicit conversions will take care of it all... no formatting is necessary...
DECLARE @SomeDateCol DATETIME
SET @SomeDateCol = '06-Sep-2008'
SELECT @SomeDateCol
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 5:16 pm
Numeric primary key... Holiday date can appear more than once depending on things like Country or State.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2008 at 5:13 pm
Viewing 15 posts - 50,251 through 50,265 (of 59,091 total)