Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't believe there are any converters for SQL to C#.</p> <p>As for approaching the creation of such a tool, I would first say, don't... your business requirement sounds like it is to get the logic into C#.</p> <p>Depending on the state of the application, you can do this in many ways: one sproc at a time; logical entities at a time (all customer logic, etc); whole hog; agile-ish where you leave the sprocs alone for the time being and call straight into them from C#, and then slowly take one of the prior approaches - always leaving yourself with a functioning application.</p> <p>Loaded question really :-)</p> <p>I personally would first try to get it working in C# straight calling into the sprocs. Then take logical entities, as you will find they may reference other sprocs. Doing a sproc at a time will fragment your C# logic during development and add extra overhead to the creation of business classes.</p> <p>The strength in a C# domain model is the clear boundaries of responsibility and grouping of behaviour into your logical entities - so taking a sproc at a time, you will not see the bigger picture. Using a converter, it will end in unreadable, unmanageable code that you then have to learn - something you don't need to do if you created it in the first place.</p> <p>So my conclusion, if there is one, is to save yourself time in the future and take this as an opportunity to redesign your business layer - as you likely have knowledge and experience of the system's production behaviour from out in the wild, so the conversion can factor in any lessons learnt.</p> <p><strong>Update:</strong> it turns out you have tooling options for the conversion. The only thing I will say to that approach is this: <strong><em>the resulting code is not going to be pretty</em></strong>. You have the benefit that your current SQL is understood by the development team - they know the code. A code generator is going to produce 100% <em>new code that no one knows</em>. Learning curve... as you are going to need to <strong><em>verify</em></strong> the output of the tool to make sure it isn't mutating your logic - no tool is infallible.</p> <p>If you decide to use the tool, I can only suggest to break the conversion down into very, very small parts (presumably the smallest is going to be a script (or perhaps even batch within a script)). When you have a small set of conversion results, integrate this into the application and pass it through a review process.</p>
    singulars
    1. This table or related slice is empty.
    1. POLooking to design a tool to Translate Business logic from Stored Procedures to C# Business Layer
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAdam Houldsworth
    1. USAdam Houldsworth
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTotally agree this... Too many variables to pull WHERE clauses into C# code and create the proper objects and architecture.
      singulars
      1. PO
      1. USshookdiesel
    2. COI have done further analysis and discovered this has more than 100K lines of PL/SQL. Would you still agree to doing this one at a time? I think it would take months of conversion work, and would be bug prone.
      singulars
      1. PO
      1. USLucas B
    3. CO@Lucas It would be equally as bug prone using a conversion tool. I would say for such a large code base, you need to review whether it is financially feasible to migrate the code. I would suggest the halfway house - get C# communicating and using your SQL as it stands, and then as you perform project iterations, make sure some conversion work is given priority. There is no easy answer, it's going to be a slog... It sounds like most of the logic is in SQL so a conversion to C# is likely going to be akin to re-writing the entire application anyway, so the testing overhead is going to be huge.
      singulars
      1. PO
      1. USAdam Houldsworth
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload