IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Yeah...me too...
I have a contractlet right now where somebody (AGAIN) is paying me because they found out that Excel isn't a DBMS. So, they want Access. Since I'm getting back into the market after about 2 years out, this is actually a decent scope for me right now.

Access has been using about 80 percent of my CPU time for the last 20 minutes. My crime? Query|New. I have no idea what the fuck it's doing. This database is fairly big for Access (~900MB), I wish I could use something better but it won't happen. So maybe it arbitrarily decided that now was the time to optimize something. Maybe it's in a loop. Maybe it's background processing SETI data. Maybe it's downloading database porn and gratifying itself. No way of knowing of course, no monitoring, no logs, no current activity to look at, jack shit.

Killing the process would solve the problem if it's just abcess looping or playing with itself or whatever but then I'd have to wait for it to repair the database, which is a lot to ask with a database of this size and a manager of this quality.

Fuck.
FAQ! We're scrod!
New ICLRPD (new thread)
Created as new thread #153863 titled [link|/forums/render/content/show?contentid=153863|ICLRPD]
     Beware Access 2003. - (acagle) - (8)
         Access 2002 does that too. - (altmann)
         Unique constraint is to blame. - (mmoffitt)
         Correct. Tables and queries share the same namespace. - (rickw) - (3)
             Re: Correct. Tables and queries share the same namespace. - (acagle) - (2)
                 Yeah...me too... - (rickw) - (1)
                     ICLRPD (new thread) - (Another Scott)
         Access Weird Behavior #233. - (acagle) - (1)
             Note: It's a bug. - (acagle)

Jump, jive and wail!
185 ms