Comments
Sort by recent activity
ok, the screenshots I was looking at were from someone else, and perhaps an earlier version. That makes sense.
appreciate the rapid response! / comments
ok, the screenshots I was looking at were from someone else, and perhaps an earlier version. That makes sense.
appreciate the rapid response!
Robert,
Sorry for the late reply, thought I would get notified of responses but maybe it went into the bit bucket. Anyway, it could have had something to do with the selection of tables we had made. We went back to the system vendor and they gave us an revised SDC template to use, and since then we've not had that error pop up. If it does again I'll try and get as much info as possible.
Glen / comments
Robert,
Sorry for the late reply, thought I would get notified of responses but maybe it went into the bit bucket. Anyway, it could have had something to do with the selection of tables we had mad...
Robert,
We're using SDC 6.1.1.308. Running it via a RDP session on a Windows Server Standard Ed SP2 server, 4 GB of ram, with a xeon 3.2 GHz processor.
The source and target databases are running on two VM sql server 2005 (no sp) boxes. The VM boxes are running Windows XP version 2002 SP2 with equivilant of xeon 2.66 processors and 900 MB of ram.
The databases are relatively small
cadence 300.75 MB sa 7 Jul 27 2007 Status=ONLINE, Updateability=READ_WRITE, UserAccess=MULTI_USER, Recovery=SIMPLE, Version=611, Collation=SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52, IsTornPageDetectionEnabled, IsAutoCreateStatistics, IsAutoUpdateStatistics 90
Cadence_dat 1 c:\data\Cadence.mdf PRIMARY 245632 KB Unlimited 15% data only
Cadence_log 2 c:\data\Cadence.ldf NULL 62336 KB Unlimited 10% log only
There are 1166 tables one of which has ~ 54K rows, a few that have ~ 24K rows, the rest are fairly small.
Thanks
Glen / comments
Robert,
We're using SDC 6.1.1.308. Running it via a RDP session on a Windows Server Standard Ed SP2 server, 4 GB of ram, with a xeon 3.2 GHz processor.
The source and target databases are running ...
Sorry, forgot to add..I tried eliminating the environment factor by installing SDC (same version) on a beefier system. It is a Windows 2003 server with 4 GB of memory and dual xeon processors. It has SQL Server 2005 SP1. Restored copies of the source and target databases to that sql instance (the databases names slightly changed of course). Yes it ran faster but..got the same memory exception errors, to the point it happened too frequently.
Glen / comments
Sorry, forgot to add..I tried eliminating the environment factor by installing SDC (same version) on a beefier system. It is a Windows 2003 server with 4 GB of memory and dual xeon processors. It...
stand by ...getting data.. / comments
stand by ...getting data..
Thanks,
I did the update, that did not help with this particular issue. I'll keep banging away at it. / comments
Thanks,
I did the update, that did not help with this particular issue. I'll keep banging away at it.