Re: Memory Management

Superboer schrieb: > Hello Fernando, > > I hate to disappoint you, however MS is not easy; try to restore a > complete level 0 backup, you will see what a can of wurms that is. > Besides that monitoring and trying to grab the hottest sql is not > easy(sqlsrv2005); the stuff described can be used; however when a > query ends, > then the needed info is stored in the relevant tables so you will > never see the hottest sql in action that also may cause you to miss a > problem sql. > > Obstacle is a leader; yeah however i still can not understand why > people accept the pile of shit. > online backup one needs the trx log and createing / restoreing looks > like how informix used to do this with onarchive which was the worst > piece of shit ever produced by informix. The data you gonna get in > your backup is when the backup ends. > Missing set lock mode to wait xxx > > DB2CV well i have not touched this nor come across this for a long > time fortunatly, if you add a container does it still redistribute all > data > in your tablespace??? and the equiv of xps, does it still give you an > error when you update a row which should cause the row to move to > another > partition; if you unload a table with blobs are blobs still written in > file.XXX where XXX goes from 000 to 999. > set lock mode to wait for the whole instance??> > > Informix is way fast and easy!!!!!! Dono about priceing; am not a bean > counter. > > > Superboer. > Hi, here I must speak up. onarchive was a superb product in those days, if used right and tested well. Ever tried ondatartr? Now, about 12 years later, there still is no utility, which is comparable to ondatartr, not even archecker. But then I know that I was one of the handful ppl who ever used onarchive in PROD on >100 servers and longer than 5 years. dic_k -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe