WPF Program Design
This may be a bit of a general question.  I'm looking for suggestions on how to design (from an architecture - I think thats the right word - perspective).  

I'm building an application that will include the following:

1) WPF Windows (Currently have this set as the main entry point)
2) SQL Server transactions (considering using [CLR SP][1] as suggested in that link)
3) And a whack of background math

I'm trying to figure out if should do all of this logic in a number of partial classes:

    public partial class MainWindow : Window

or if I should code the SQL material in a separate class... etc.  

Any thoughts, suggestions are much appreciated!  

P.S.  The SQL connection will have be kept open the entire time, if that makes a difference 


  [1]: http://stackoverflow.com/questions/2152516/c-sql-database-listener-help-needed
WPF Program Design
===

This may be a bit of a general question.  I'm looking for suggestions on how to design (from an architecture - I think thats the right word - perspective).  

I'm building an application that will include the following:

1) WPF Windows (Currently have this set as the main entry point)
2) SQL Server transactions (considering using [CLR SP][1] as suggested in that link)
3) And a whack of background math

I'm trying to figure out if should do all of this logic in a number of partial classes:

    public partial class MainWindow : Window

or if I should code the SQL material in a separate class... etc.  

Any thoughts, suggestions are much appreciated!  

P.S.  The SQL connection will have be kept open the entire time, if that makes a difference 


  [1]: http://stackoverflow.com/questions/2152516/c-sql-database-listener-help-needed