> > > A simple update query, over roughly 17 million rows, populating a > > newly added column in a table, resulted in an out of memory error > > when the process memory usage reached 2GB. Could this be due to a > > poor choice of some configuration parameter, or is there a limit on > > how many rows I can update in a single statement? > > > > I believe that it is plataform problem. Because on *nix this limit > don't occur. But I don't specialist Windows. On most Windows Servers(except for database edition and a few other variants), 2Gb is the most you can address to a single process without booting the machine with a special parameter called \3G which will allow for allocating up to 3Gb per process. That is the limit unless you get special versions of windows server 2003 as far as I know. If you do a google search on \3G with windows you will find what I am refering too. Hope that helps a bit. Cheers, --- Curtis Gallant cgallant@xxxxxxxxx ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend