How does MS Access impact Tempdb?
-
Does anyone have any insight as to how linking your Access data project to SQL Server tables affects tempdb? I can guess that if you are sorting or doing joins between the SQL Server tables it takes place in tempdb. Is there any way to measure the impact? Thanks.
There is no "i" in team, but idiot has two. -
Yes.
Ideally you have a performance benchmark for your system right now? If not, I would suggest running it for a couple of hours minimum, but preferably longer to build up an idea of query execution times.
I would look at profiler traces, performance monitor counters. When linking in Access, I would run the same traces/counters and make a direct comparison.
Typically, you know when tempdb is being hammered when you are in enterprise manager and you refresh the view on tempdb. In our environment, if tempdb is being hammered, we can wait minutes before the taskpad view is refreshed!
-
"Typically, you know when tempdb is being hammered when you are in enterprise manager and you refresh the view on tempdb. In our environment, if tempdb is being hammered, we can wait minutes before the taskpad view is refreshed!"
Well, I should quit whining, then. We don't have that problem at all, thank goodness.
The server is still chugging along.Our problem is that tempdb grows and grows until it fills the disk, due to our data warehouse load. We already have tempdb alone on a disk, and have added an additional file to tempdb on our main data disk.
One "feature" of our data warehouse load is that it pulls millions of rows from a linked server (SQL Server 2000) in a bunch of "INSERT INTO tablename SELECT * FROM otherserver.database.dbo.tablename" statements. Does that make use of tempdb? If so, how?
There is no "i" in team, but idiot has two.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply