Viewing 15 posts - 39,901 through 39,915 (of 59,098 total)
I believe there might be a bit of a language barrier problem here... I believe the OP is saying that, yes, he has thousands of tables and millions of rows,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2010 at 8:39 am
Please see the following article... it has code to do nearly precisely what you want and will also zero fill any missing data. The best part is, you won't...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:46 pm
Grinja (2/5/2010)
That could work ... thanks for the suggestion!
Which unprintable characters? Just any character less than CHAR(32)???
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:32 pm
Ramesh Saive (2/5/2010)
I don't think so there is any equivalent function in SQL Server. But you can create you own function using the existing REPLACE function.
Heh.. Let's see some...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:31 pm
Don't even try to salvage the code. Sit down and write a new set of requirements for the code without thinking about how to code it. Then, sit...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:28 pm
lmu92 (2/4/2010)
Duplicate post.Please continue discussion here.
I guess you guys kind of missed that one, huh? 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:26 pm
Stefan Krzywicki (2/4/2010)
REVERSE will make the trailing whitespace into leading...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:24 pm
BaldingLoopMan (2/5/2010)
create table #temp
(
offerid int
, Catg varchar(100)
)
insert into #temp( offerid, Catg )
select 1, 'health' union all
select 1, 'fitness' union all
select 1, 'weights' union all
select 2, 'personal' union...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:22 pm
It sounds like the optimizer is using a cached plan which doesn't necessarily meet the needs of the criteria for the current query. If you're using a stored proc...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:20 pm
David McKinney (2/5/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:10 pm
WayneS (2/5/2010)
Does this do what you want?
select top 26 replicate(char( row_number() over (order by object_id)+64),3)from sys.objects
Heh... I can't tell if they want a split function or what you...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:06 pm
vyas (2/5/2010)
Use union
Please show us how. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:03 pm
If you use WITH(TABLOCKX), no one but you will get in once everyone else gets out. The "X" stands for "exclusive".
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:02 pm
Cool. Thanks for the info.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 9:00 pm
Jim,
There are a lot of things that can affect performance. As a result, we need more information. Take a look at the article in the 2nd link in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2010 at 8:52 pm
Viewing 15 posts - 39,901 through 39,915 (of 59,098 total)