Hi
I contacted my postmaster and it seems that the emails from you got stuck at our spam filter without letting anyone know about it.
I was quite surprised not receiving response from you, because your support has always been really quick, and it seems that the only thing that failed in this case was our spam filter
Thanks for quick response, and a great product.
Regards,
Haukur
Search found 3 matches
- Mon 20 Dec 2010 14:14
- Forum: dotConnect for Oracle
- Topic: DotConnect for Oracle 6.00: Download possible
- Replies: 9
- Views: 1429
- Mon 20 Dec 2010 07:46
- Forum: dotConnect for Oracle
- Topic: DotConnect for Oracle 6.00: Download possible
- Replies: 9
- Views: 1429
- Wed 27 Oct 2010 11:46
- Forum: Entity Developer
- Topic: Problem with lot of schemas
- Replies: 2
- Views: 1724
Problem with lot of schemas
Hi
I have a problem when i connect to oracle database that have a lot of users. In my case, there are about 100.000 users, and each has one logon-trigger. When I create a connection in entity developer, and click "show all objects" because I need to map an object that is in another schema, entity developer loads all users and eats up all the memory in my machine. What is should do is only show schemas that contains objects that I have access to like Visual Studio server explore does.
Is there somewhere an option that I can set to stop loading all users/schemas, because otherwise I always have to log on as each schema owner.
Regards,
Haukur
I have a problem when i connect to oracle database that have a lot of users. In my case, there are about 100.000 users, and each has one logon-trigger. When I create a connection in entity developer, and click "show all objects" because I need to map an object that is in another schema, entity developer loads all users and eats up all the memory in my machine. What is should do is only show schemas that contains objects that I have access to like Visual Studio server explore does.
Is there somewhere an option that I can set to stop loading all users/schemas, because otherwise I always have to log on as each schema owner.
Regards,
Haukur