Viewing 15 posts - 41,341 through 41,355 (of 59,069 total)
Crap... I can say "crap" on this post, right? Crap, crap, crap... it's happened again same as last year and for the same reason. Started a new job...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2009 at 8:00 pm
Brad Allison (10/26/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2009 at 10:09 am
Krasavita (10/26/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2009 at 10:06 am
Brad,
Just change CompletedDate and CompletedShift aliases to ScheduledDate and ScheduledShift because those are what you seek.
As for the other thing, I assumed you were using SQL Server 2005 because this...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2009 at 7:57 am
Silverfox (10/26/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2009 at 6:13 am
GilaMonster (10/26/2009)
Jeff Moden (10/25/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2009 at 6:02 am
You may want to avoid PIVOTs in favor of the old fashioned but tried and true crosstab after reading the following article...
http://www.sqlservercentral.com/articles/T-SQL/63681/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 10:37 pm
I can click and drag a column name both in QA and SSMS so I don't really care how long they are.
What I do care about is a column name...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 10:29 pm
Yep... create a new role on the database that has no privs to anything except the view and use that role to "Get External Data" in Excel.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 10:10 pm
Why not just drop the date ranges into a table and forget the month stuff?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 10:06 pm
Jay_dba (10/25/2009)
CREATE TABLE #IMaster (ID INT, ITEM1 VARCHAR(100))
GO
INSERT #IMaster
SELECT 1,'pencil'
UNION
SELECT 2,'pen/pencil'
UNION
SELECT 3,'ink'
UNION
SELECT 4,'pen/pencil/ink/'
I need to create a view like this
IDid1 ITEM1
11pencil
21pen
22pencil
31ink
41pen
42pencil
43ink
We are still...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 10:02 pm
Oh... be careful, Johan... XML splits are relatively slow compared to many other methods.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 10:00 pm
One "best practice" is to make sure the calculated column results in a "Determinant" result so that it can be indexed if you need it to be.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 9:57 pm
repent_kog_is_near (10/25/2009)
Example of these data:
50.6%
6.50% tax
1025.25...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 9:53 pm
OK... I'm confused... I thought that one of the major reasons for having a Clustered Index was so that it would reorg the data so that it wasn't fragmented and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2009 at 9:48 pm
Viewing 15 posts - 41,341 through 41,355 (of 59,069 total)