January 30, 2008 at 8:56 am
Hi Guys!
i'm still a junior DB Developer with a problem in one of the solutions i work on;
at work we have a system that get data from an ftp site and sends to the database. another one reads the same data from the Db and processes it........the problem is our database reads always time-out and if we increase the time it works but is very slow.
what other alternatives besides the index tables or can index tables be manipulated to accomodate the kind of situation.
thanks
January 30, 2008 at 11:23 am
Could be indexes, could be the queries, could be blocking. Without more information it's very hard to say.
Can you post the query that times out and the schema and indexes of the tables involved?
If you run the query in management studio, how long does it take. While running it, if you look at the sys.dm_exec_requests view, what's the query's wait type? Is it blocked by another process?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 30, 2008 at 11:36 am
In general you want to make sure you use bulk logging during any data loads and optionally drop the indexes just before the load then readd them after the load.....another thought, make sure the file you are loading is physically on the sql server....if the file is on a network share across the building that could significantly slow you down?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply