Recent content by Delo123

Hi Tom, Why avoid Raid 5. What do you advise? Raid 10?

Gave the Server a new SID, took it out of the domain, rejoined, now everything is ok. Don´t know why, but it works... pfff... 2 days for nothing :( Thanks guys

Servers by broker show SV0 Pid 3236 Login TCP Port 2305 (2305 is what i definded on database startup) SV1 Auto Port 3000. No Firewall running on the 2008 nor on the Client (Windows Firewall disabled on both, no other firewall/virus) Should i be able to telnet from a client? Telnet...

We are just updating 9.1D --> 10.1C. Win 2008 X64 Enterprise Server. Database is converted, everything running ok. When I start the Client on the localhost everything is fine But I am unable to connect from a Client Machine. I've installed Client networking, setup my pf, but getting Error 10060...

I`ve done the same on Progress 9.1D. Just kill the ISDEL once install is started. X64 gives a major Performance benefiteven on 9.1D ! But ofcourse you SHOULD update! ;)

Progress 9.1D (Sadly enough unable to update at this Time, because the Main Application is compiled in 9 and do not have the Source Code). Data is pumped over LAN to the Workstation (1gb lan). I will try to hook a workstation up with a HBA and see if this improves performance. Yes, the Queries...

Hi Tom, Actually I am restoring to 4 Different Servers (Workstations actually) After the Restore we do Dbtool (due to field length) and then mount each database and let SAS pull the Data out. The SAS Task used to take 12 Hours on one Workstation, so now we splitted it into 4. Then again now...

But I need to restore the same Database multiple times. No other options? Some way around? I also don`t understand why Progress locks the Backup file, it doesn't have to write, right?

I run following task to restore our DB each night for our Datawarehouse It is apprx 70Gb and takes 1.40Hours from our SAN call "c:\Program Files\Progress\bin\prorest" training \\dc01-grnpwr\backupMOS\mos.bck I noticed the restore routine only uses one physical CPU Core, is it somehow...

The File Locking wonders me also, but this is the Answer I received from Progress Support: I get the same behaviour with the prorest. The prorest command does indeed open the file with some exclusive lock. This is done to prevent anything interfering with the restore. There is no workaround...

Since it is freshly restored why does it need to be backuped again before I can copy it? But I will try the incremental. For the sync/split do you mean replication? we do not use that at the moment since we have to make changes to the restored databases so i think starting replication each day...

For our Datawarehouse we need multiple copies of our Database each night. At the Moment we do an online Backup, and restore it multiple times each night, but since the Backup File is locked by the Restore Util we have to each after another. Since our main DB is 58GB we are running out of Time...