
| |
| View previous topic :: View next topic |
| Author |
Message |
administrator Developer


Joined: 24 Jul 2004 Posts: 4750 Location: King William, VA
|
Posted: Thu Jul 26, 2012 7:47 pm Post subject: |
|
|
I'm afraid I wouldn't have the time to do something like that. Wish that I could.
If you ever do rebuild the system and find that SQL Server is normal afterwards, that would be good to know.
Regards |
|
| Back to top |
|
 |
sundown New User

Joined: 05 Oct 2012 Posts: 1 Location: Edinburgh, Scotland
|
Posted: Fri Oct 05, 2012 12:52 pm Post subject: |
|
|
I am finding Newsman unusable now after going to the latest release (3.0.7)
set @vSQLText = 'DELETE #TempPartImport FROM #TempPartImport INNER JOIN '+@pPartsTable+' ON '+@pPartsTable+'.MessageRef = #TempPartImport.MessageRef WHERE '+@pPartsTable+'.MessageRef IS NOT NULL'
was taking 1583971 milliseconds ... DISC IO is way too high ..
have stopped using NewsMan and using Grabit .. pity ... NewsMan was a cool app |
|
| Back to top |
|
 |
administrator Developer


Joined: 24 Jul 2004 Posts: 4750 Location: King William, VA
|
Posted: Fri Oct 05, 2012 2:08 pm Post subject: |
|
|
For it to be that slow, there has to be a reason. I never see anything like that using SQL Server on a 2007 PC.
* How many records are in the parts table being referenced at the time?
* Have you purged your database lately?
* How much memory have you allocated to SQL Server?
While SQL Server does use a lot of disk I/O, it is manageable if there is sufficient RAM to allow SQL to cache active transactions.
If your PC has difficulties with SQL Server, you should take a look at switching to MySQL.
Regards |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|
Copyright 2003-2006, Daniel Cumpian
NMP Default By ::Dementeddogz.com::