Viewing 15 posts - 39,541 through 39,555 (of 59,098 total)
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
{edit} Never mind... misread the post...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 9:21 pm
Nikki-395727 (3/2/2010)
I knew that this is the best I can do with the current set up but wanted to confirm.
I just feel bad that all our...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 9:06 pm
Paul White (3/3/2010)
For general advice, and a solid methodology that works, read This Microsoft White Paper.
BWAA-HAAA!!! 😛 The very first item in the "Common scenarios to avoid in OLTP"...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:57 pm
dakshinamurthy-655138 (3/1/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2010 at 8:50 pm
Viewing 15 posts - 39,541 through 39,555 (of 59,098 total)