Interestind DB Server Setup

Question

Hi I work at this place that it does almost everything row-by-row. And also almost all the core business logic uses triggers.
And because of that there is a need to implement an application lock so the triggers would not cause dead-lock.
From the observations, it got everything wrong pretty much for Efficient Oracle Coding Practicing...
And it looks like they compensate this bad coding practicing by having a very large db server setup as shown below.
Now I was told that they are migrating to SQL server for the backend db backend. This sounds pretty intriguing as I only heard of migrating from SQL server to Oracle for backend DB engine.
Below are the server setup....also it looks they dont use bind variable very well in the existing code base. Perhaps you guys can shed some lights on that and share some interesting stories about very bad practice....?
SQL> show sga
Total System Global Area 9.5748E+10 bytes
Fixed Size                  2368664 bytes
Variable Size            1.2033E+10 bytes
Database Buffers         8.3702E+10 bytes
Redo Buffers               10813440 bytes
SQL> show parameter pool
NAME                                 TYPE        VALUE
_shared_pool_reserved_min_alloc      big integer 4000
buffer_pool_keep                     string
buffer_pool_recycle                  string
global_context_pool_size             string
java_pool_size                       big integer 208M
large_pool_size                      big integer 512M
olap_page_pool_size                  big integer 0
shared_pool_reserved_size            big integer 100M
shared_pool_size                     big integer 10G
streams_pool_size                    big integer 512M
SQL> show parameter cpu
NAME                                 TYPE        VALUE
cpu_count                            integer     96
parallel_threads_per_cpu             integer     2
SQL> with m1 as (
  2  SELECT substr(sql_text,1,40) "SQL",
  3           count(*) cnt,
  4           sum(executions) "TotExecs"
  5           FROM v$sqlarea
  6           WHERE executions < 5
  7           GROUP BY substr(sql_text,1,40)
  8           HAVING count(*) > 30
  9           ORDER BY 2
10  )
11  select sum(cnt) from m1;
  SUM(CNT)
    123192

Answer 1

>
Perhaps you guys can shed some lights on that
>
I think I'm already blinded by the light you have shone on it.
Can you please check and confirm that you are not actually already using SQL Server and perhaps don't realize it? All of the things you have mentioned seem to fit well with SQL Server environment.
>
they are migrating to SQL server
>
I absolutely agree with this decision. You are already using many SQL server techniques that should only be used on SQL server.
1. The row-by-row processing - this should fit well in a SQL server environment - not for Oracle
2. Putting business logic in triggers - SQL server does this a lot - not for Oracle
3. Using application locks to avoid deadlocks - definitely SQL server - shouldn't be wasting these in an Oracle setup
4. got everything wrong pretty much for Efficient Oracle Coding Practicing - again SQL server - it's hard to do this in Oracle
5. current developers expertise - based on what you described they must know SQL server pretty well. At least they don't know Oracle.
They would be happier using these techniques in SQL server where poor performance for these things will be masked by the even poorer performance of everything else. They will fit into SQL but stick out like a sore thumb in any decent Oracel environment.
Have you updated your resume?