Viewing 15 posts - 35,326 through 35,340 (of 59,099 total)
It's an interesting problem because the supposed "set-based" methods that immediately come to mind are all going to be Triangular Joins which will be much slower than any kind of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2011 at 5:30 am
moadh.bs (1/19/2011)
I'm trying to select specific rows from this table:
CREATE TABLE MVTS (idMvt1 int,
idMvt2 int,
idMvt3 int);
INSERT INTO MVTS
SELECT 271, 204, 136
UNION ALL
SELECT 271, 202, 136
UNION ALL
SELECT 268, 253, 204
UNION...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2011 at 4:44 am
ezimmerman 33749 (1/18/2011)
Task Table
-----------
Id [Guid]
Name [nvarchar(64)]
ParentId [Guid]
Time Entry Table
-----------------
Id [Guid]
EntryDate [DateTime]
HoursCharged [float]
TaskId [Guid]
1. I would like to load the entire hierarchy of a parent...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 9:29 pm
romanoplescia (1/17/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 9:24 pm
sqldba_icon (1/18/2011)
Seems like its always been the same..i will further investigate..
With that many reads, it is possible that the query has an "accidental" Cross-Join in it in the form of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 9:21 pm
I absolutely agree with Gail and Elliott. Having Date and Time in separate columns is usually going to cause more problems than it fixes. To repeat what Gail...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 9:17 pm
tacy.highland (1/18/2011)
I'm a little nervous on the MERGE code since I'm not familiar with it. Can i assume that, while not best practice, the UPDATE FROM...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 9:08 pm
drew.allen (1/18/2011)
Carl Federl (1/18/2011)
1. subtract one-half of a day and subtract 2 milliseconds, which is 43200002...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 8:59 pm
The following should help. Be advised that a revision to make it faster for higher byte counts is in the works must not much will touch it for strings...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 8:55 pm
Heh... possibly even more fun... just swap the extensions on the data and log file names. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 7:41 pm
From the article...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 6:56 pm
Heh... and what form of age discrimination will this be used for? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 12:47 pm
chaudharyabhijit (1/17/2011)
Thank you for the suggestion. I would love to do what you asked me but unfortunately these tables are from a really obsolete software and there is no...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 7:31 am
keymoo (1/18/2011)
Jeff Moden
Just to follow up on that... a good ol' fashioned cross-tab can make life real easy and "prettier".
SELECT Symbol,
SUM(CASE...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 7:29 am
Bryan McGuire (1/17/2011)
I have been given a task to create a pivot table from a table of data supplied via a 3rd party.
The table is structured like this...
CREATE TABLE [dbo].[EntityRiskGroupKeyItem](
[Name]...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 11:21 pm
Viewing 15 posts - 35,326 through 35,340 (of 59,099 total)