Viewing 15 posts - 43,276 through 43,290 (of 59,063 total)
Jeff Moden (6/21/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2009 at 11:20 am
Just to be clear on another point... it's not the shrinking of a database that causes fragmentation and performance problems. It's the regrowth that causes all of that. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2009 at 11:16 am
Jeez... here's something I absolutely hate to see...
http://www.sqlservercentral.com/Forums/Topic738870-361-1.aspx
I suppose it's because people just don't know enough about databases to know better than to think they can just jump in and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2009 at 10:50 am
Paul White (6/21/2009)
Jeff Moden (6/20/2009)
Oh yeah... now I remember. One column needed to be split (a portion isolated, really) from the middle.
Fascinating thread. I just spent the last...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2009 at 10:42 am
Florian Reischl (6/21/2009)
Do you use any clipboard manager tool?
No and that's a major part of my point... if you copy and paste into SSMS from the good code example I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2009 at 10:32 am
Gosh... there's just no way to say this without ticking someone off. My apologies in advance....
This doesn't sound like a trivial undertaking. It sounds like this database could...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2009 at 10:20 am
Heh... well done, Paul. You should have written the article. Thanks for taking the time.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2009 at 1:10 am
WayneS (6/20/2009)
Jeff Moden (6/20/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 11:59 pm
WayneS (6/20/2009)
Jeff Moden (6/20/2009)
WayneS (6/20/2009)
Jeff Moden (6/17/2009)
Ummmm.... my rule of thumb is to peel one potato at a time on the quirky update...
Hey Jeff, I remember reading a post...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 11:41 pm
Paul White (6/20/2009)
Jeff Moden (6/20/2009)
It would be really helpful if several other IE users started throwing rocks at this annoying problem.
Hey Jeff,
So yeah - I'm game - at whom should...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 11:16 pm
Heh... Ok... Remember... you asked.:-)
Here's why... the original code looks like this (for example)....
[font="Courier New"]--===== Create and populate the Tally table on the fly
SELECT TOP 1000000 --equates to more than 30 years of dates
IDENTITY(INT,1,1) AS N
INTO dbo.Tally
FROM Master.dbo.SysColumns sc1,
Master.dbo.SysColumns sc2
--===== Add a Primary Key to maximize performance
ALTER TABLE dbo.Tally
ADD CONSTRAINT PK_Tally_N
PRIMARY KEY CLUSTERED (N) WITH FILLFACTOR = 100
--===== Allow the general public to use it
GRANT SELECT ON dbo.Tally TO PUBLIC[/font]
If I throw that code into a code window in the presence of IE,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 11:13 pm
smsam1 (6/20/2009)
i want to store only T or F in the flag field . for example if i enter 't' it should be stored as 'T' and vice versa.
Why? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 10:41 pm
haroonrashed786 (6/20/2009)
but..i have to use CLR triggers only
As previous suggested, you really need to tell us why you are constrained to using only CLR triggers. Even CLR experts like...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 10:39 pm
akash.suryan (6/18/2009)
Thanks Grant.....I will love to see those questions please let me know.....
You missed the point. After the first two or three questions, the questions are mostly not planned....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 10:33 pm
It's probably not the answer you want to hear but, there's a large amount of functionality in many stored procedures that simply cannot be migrated to a function. Just...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2009 at 10:13 pm
Viewing 15 posts - 43,276 through 43,290 (of 59,063 total)