Viewing 15 posts - 39,511 through 39,525 (of 59,072 total)
Karen Lopez - InfoAdvisors (3/2/2010)
These tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2010 at 12:24 am
Ah... good that some have seen the movie.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2010 at 12:16 am
TheSQLGuru (3/3/2010)
Looks like this might be a dead thread now Jeff...
Aren't you glad it wasn't? I had a good feeling about this one...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2010 at 12:14 am
dakshinamurthy-655138 (3/3/2010)
for not replying to the thread, as i was not feeling well i was off from the office.
The reason why i need this is, one of my client need...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2010 at 12:13 am
Roust_m (3/3/2010)
Jeff Moden (3/3/2010)
Roust_m (3/2/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 11:52 pm
Before you simply "move on"... what would be wrong with simply adding the creation of the correct indexes to the process?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 11:02 pm
Hi Joe and welcome aboard.
Most folks like to test their code before they post it but don't have the time to build test data to do it with. Keeping...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 10:58 pm
Personally, I think it would be a much better thing to convince the user of the error of their ways.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 10:48 pm
Adam Bean (3/3/2010)
Having some troubles here. The query I'm working on takes 34 seconds, which in itself is obviously unacceptable. The indexing is rather good, but can be tweaked...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 10:41 pm
harshalnag (3/3/2010)
Each user can buy what he wants to and check out....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 10:32 pm
itskumar2004 (3/3/2010)
Here is the update statement:
update set
deletedate=getdate()
from
dbo.A
where
deletedate is null
and UserID in (select UR.UserID from
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 10:27 pm
Jeff Kring (3/3/2010)
I did look into ROW_NUMBER as an option. I could use it to return the correct rows, but the application needs the actual value as well.
Not sure...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 10:19 pm
With hardly an exception, my stance is that users who write their own queries should not have access to the production server... period. A separate "report" instance is the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 10:02 pm
What ray means is that you simply need to not insert duplicated data.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 9:45 pm
"All the above" depending on what the customer has. It's also not a really good question because of things like the Enterprise Edition of any version is "better" than...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 9:41 pm
Viewing 15 posts - 39,511 through 39,525 (of 59,072 total)