Is there going to be a new Beta Release ..

• 
  Indeed, that sounds about right. You *can* run SQL Prompt with a database of that size (we have a very large SAP database we use for this), and once it's pulled in the meta-data and built up its internal data structures it should perform very well indeed. However you need to have an awful lot of physical memory on your machine to make this realistic: I'd say if you're working with a database of this size you need a good 2GB of physical memory. In the final release we'll provide the ability to blacklist databases and even whole servers so that SQL Prompt won't load meta-data from them.
  
  
  HTH,
  Bart

  Bart Read September 08, 2006 10:09

  - 0 +
• 
  Wow ... 2 GB of internal Memory. I got a nice little notebook with 1 g but I am sure getting an extra gig just for this will not happen. It looks like it get all columns , Indexes messages etc .. But it is Diing at the time of Saving the File it never finishes. There must be something amiss there
  
  w

  travelingwilly September 08, 2006 10:29

  - 0 +
• 
  Hmm OK, that's interesting. It would probably take quite a long time to actually save a cache file that large. What's the CPU/HDD doing whilst this is happening? If there's activity on both fronts I'd expect that this is exactly what's going on. Best thing to do is trying leaving it for a while, maybe set it off when you leave in the evening or something.
  
  
  Thanks,
  Bart

  Bart Read September 08, 2006 10:49

  - 0 +
• 
  On the Bottom Of the Screen in the new handy dandy status.. I see it going thru Getting Coumn , Messages , index I do not remember what SO it seems to be pulling info relativly fast mayby 5 minutes for all . I am assuming it is a one time thing so that is okay .. BU then the saving goes into lalla land I look at the task it was using about 1,023.22.. 1 g I am assuming and 99% of system resources. I even left for 15 minutes and it was still working... or doing something since I did not see and Disk activity

  travelingwilly September 08, 2006 11:13

  - 0 +
• 
  Interesting. Can you do me a favour and try taking a snapshot of the database with SQL Compare please? If you don't have it you can download a fully functional trial version from the main website.
  
  SQL Compare and SQL Prompt use the same meta-data model so I'd be interested to see whether or not it works in SQL Compare. If it does then it's something we're doing, if not then I get to blame somebody else!
  
  Generally unless you clear the cache it only needs to load the meta-data from the database itself once, from then on it uses its cached copy (which btw is encrypted and can only be read from your user account). You might want to clear the cache if you've made a lot of changes to your database though to force SQL Prompt to reload the meta-data from the database.
  
  
  Thanks,
  Bart

  Bart Read September 08, 2006 11:17

  - 0 +
• 
  Okay I down loaded compare and ran it .. Against 2 DB it took approx 15 minutes and I could see resources fly up to 1 gig and use from 80 to 995 CPU.. BUt still better that Prompt3 ... Please note when I used SQL P 2 I had simmilar issues so I dropped the prospect of looking for tables and just look for Fields but at least it work I downloaded the Compare to XML. As EXCEL it exploded.
  You also mentioned about Saving in Cach. Peoplesoft at time recomends Cache is small and refreshed alot
  
  w

  travelingwilly September 08, 2006 16:09

  - 0 +
• 
  Sorry, I think you misunderstood what I meant. What I'm asking you to do if you have time (I'm assuming you're using SQL Compare 5), is to compare the databases and then take a snapshot of the large peoplesoft database by clicking on the appropriate option on the File menu in SQL Compare. You don't need to do anything fancy: you can either compare the Peoplesoft database to itself or, and this is probably better, to an empty database, but make sure you take the snapshot of the Peoplesoft database. Again, if you don't have time don't worry, but it would be extremely useful for us to know what happens.
  
  Also the additional memory usage in SQL Prompt 3 over SQL Compare is likely due to the additional complex data structures that SQL Prompt has to maintain.
  
  
  Many thanks,
  Bart

  Bart Read September 11, 2006 06:03

  - 0 +

Add comment

Please sign in to leave a comment.