Viewing 15 posts - 286 through 300 (of 508 total)
What you really need in your table is an event type - Clock In or Clock out - not just a time.
I've worked on a couple of time card type...
January 25, 2011 at 2:28 pm
Does a person only clock in and out once per work day? Can someone clock in for work, clock out for lunch, clock back in again after lunch and...
January 24, 2011 at 12:47 pm
Aside from taking toddasd's suggestion to combine the 2 different insert statements into 1, which I heartily agree with, I've worked with SQL 2000 and 2005 with MS Access and...
January 20, 2011 at 3:50 pm
You could try the suggested index, but I doubt that it would have any effect on the Insert operation. The suggested index has nothing to do with the columns...
January 20, 2011 at 2:37 pm
ZL,
One of the reasons I suggested splitting up the merge operations was to establish without a doubt what exactly was taking the most time. From my experience inserting is...
January 19, 2011 at 12:34 pm
Just for testing purposes you may want to break out the UPDATE and INSERT into 2 different steps (doing an UPSERT the old fashioned way). Update what's there and...
January 18, 2011 at 1:10 pm
Divya,
Glad to be of help.
Todd Fifield
January 15, 2011 at 7:21 pm
Damn! I thought I'd never say this but score 1 for Joe.
Actually the FROM syntax is very useful as a previous poster mentioned in that the UPDATE can be...
January 14, 2011 at 12:40 pm
Here are the steps to allow distributed ad hoc queries:
sp_configure 'show advanced options', 1
reconfigure
sp_configure 'Ad Hoc Distributed Queries', 1
reconfigure with override
This should handle the problem.
Todd Fifield
January 14, 2011 at 11:38 am
Excellent article Gail! Very simple and easy to understand with the fundamentals that add up to a good understanding of the subject.
These articles should be required reading for both...
January 14, 2011 at 11:15 am
To amplify a bit on what Grant wrote. It's very difficult to estimate the future performance of a query based on it's execution plan. A query may perform...
January 13, 2011 at 4:16 pm
Jeff,
The main reason for using a sequence table is so that each store and even each register can have their own sequence of tickets.
The ticket numbers for the stores might...
January 11, 2011 at 7:34 pm
Jeff Moden - 1/10/2011
Why can't you just add the IDENTITY property to the UNQ_ID column? It will help you avoid a whole lot of headaches including but certainly not limited...
January 11, 2011 at 2:22 pm
I did something like this some years ago and I don't have the code available or I'd just paste it here for you. The application had to do with...
January 11, 2011 at 2:03 pm
Chad,
I would try to politely embarrass the 3rd party into allowing a dummy column in the sequence table. After all, a table with a single Identity column is pretty...
January 10, 2011 at 11:03 am
Viewing 15 posts - 286 through 300 (of 508 total)