June 26, 2012 at 6:57 am
Hi All,
A week ago,to solve the disk space issue.I had moved the ntext columns of a table to some other filegroup in a different by which we got the space.
After that we are observing insert statement into this table is taking a long time than normal like 400 sec just to insert a single record.
For your information ,there is not much indexing is there on this table as it is used less frequently and what ever the insert statement taking long time is having huge amout of ntext data.
Is this due to change of filegroup and disk for the ntext data.Is it necessary to rollback the changes or Is there any other way to solve this issue.
Regards,
Ranjith
June 26, 2012 at 7:47 am
Not enough information to tell you precisely what the solution might be. Is the disk you moved the storage to in the exact same configuration and speed as the disk it was on previously? If they're not the same, what's different? That might be the issue right there. If the query is running slowly, use extended events to capture the wait processes for that query to understand what it's waiting on. That can tell you where the problem is. It's unlikely that this type of structural change will lead to different execution plans, but I'd check it anyway to understand what's occurring when you do the insert.
Start gathering all that data. It should lead you to a solution.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 26, 2012 at 8:01 am
HI
Both the disks are having the same configuration and are at same speeds.
We only moved the ntext columns to the second disk ,other columns remained intact in first disk only.
I will try to find what the query is waiting for.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply