Transact SQL Query

Question

Hi,
We are using sql server 2012. This query is used by financial applications. Each client has multiple accounts. There will be multiple transactions happening on each account (like deposit, withdrawal, sale money, internal transfers etc).
Eg:
TransactionID
Type
Incoming Account#
Outgoing Account #
Date
Amount
1000
Deposit
1101
01/01/2014 7:30 AM
500.00
1001
Withdrawal
1101
01/02/2014 7:00 AM
300.00
1002
Internal Transfer
1101
1102
01/02/2014 8:00 AM
100.00
1103
Withdrawal
1102
01/04/2014 9:00 AM
50.00
This is just sample to get feel. I need to take so many other criteria into account when checking whether particular account has enough amount. All the above transactions belong to 1 client.
 In above table, account 1101 got money 600/- but 300.00 got withdrawn. So, account has enough money
What I was doing in a loop call another stored procedure and pass transaction for calculations based on criteria and finally come up with whether account has sufficient amount and mark it in a table for that account. Next send next transaction to the stored
proc in a loop and check the amount sufficiency. In the above example, I go in loop and call another stored procedure for account 1101 3 times.
So, it is taking long time and we are getting timeout error. Is there any other efficient way of handling this for a particular date range.
I appreciate your response.
Thanks,
Spunny

Answer 1

>> We are using SQL Server 2012. This query is used by financial applications. Each client has multiple accounts. There will be multiple transactions happening on each account (like deposit, withdrawal, sale money, internal xfers etc). <<
Please post DDL, so that people do not have to guess what the keys, constraints, Declarative Referential Integrity, data types, etc. in your schema are. Learn how to follow ISO-11179 data element naming conventions and formatting rules. You are totally ignorant
on this basic standard. Temporal data should use ISO-8601 formats (you failed! So we have to edit everything). Code should be in Standard SQL as much as possible and not local dialect. 
This is minimal polite behavior on SQL forums. Now we have to guess and re-type your data for you. Also, do not post pictures. We are not small children who cannot read. We use DDL. 
There is no generic “type" in RDBMS. There is no generic “date" in RDBMS. In fact DATE is a reserved word in SQL!! There is no generic “amount" in RDBMS. You cannot use # in a column name; it violates ISO standards. 
Here is my guess, with clean up. 
CREATE TABLE Transactions
(trans_id CHAR(4) NOT NULL PRIMARY KEY, 
 trans_type VARCHAR (15) NOT NULL
   CHECK (trans_type IN 
    ('Deposit', 'Internal xfer', 'Withdrawal')), 
 in_acct_nbr CHAR(4), 
 out_acct_nbr CHAR(4), 
   CHECK ((in_acct_nbr + out_acct_nbr) IS NOT NULL),
 trans_date DATETIME DEFAULT CURRENT_TIMESTAMP NOT NULL, 
 trans_amt DECIMAL (12, 2) NOT NULL
   CHECK (trans_amt > 0.00));
INSERT INTO Transactions
VALUES
('1000', 'Deposit', '1101', NULL, '2014-01-01 07:30:00', 500.00), 
('1001', 'Withdrawal', NULL, '1101', '2014-01-02 07:00:00', 300.00), 
('1002', 'Internal xfer', '1101', '1102', '2014-01-02 08:00:00', 100.00), 
('1103', 'Withdrawal', NULL, '1102', '2014-01-04 09:00:00', 50.00); 
>> What I was doing in a loop call another stored procedure and pass transaction for calculations based on criteria and finally come up with whether account has sufficient amount and mark it in a table for that account. <<
You are mimicking a traditional ledger in SQL. This double entry model goes back to a monk named Luca Pacioli in the 1400's; he used Roman numerals and has no negative numbers. Today, we use Arabic numerals, negative numbers and matrices. Why are you looping?? 
Here is a skeleton of a modern version of a ledger. 
CREATE TABLE Transactions
(trans_id CHAR(4) NOT NULL, 
 acct_nbr CHAR(4) NOT NULL,
 PRIMARY KEY (trans_id, acct_nbr),
 trans_date DATE DEFAULT CURRENT_TIMESTAMP NOT NULL, 
 trans_amt DECIMAL(12,2) NOT NULL,
 CHECK (trans_amt <> 0.00),
 trans_type VARCHAR(15) NOT NULL
 CHECK (trans_type IN 
 ('Deposit', 'Internal xfer', 'Withdrawal')),
INSERT INTO Transactions
VALUES
('1000', '1101', '2014-01-01', +500.00, 'Deposit'), 
('1001', '1101', '2014-01-02', -300.00, 'Withdrawal'), 
('1002', '1101', '2014-01-02', +100.00, 'Internal xfer'), 
('1002', '1102', '2014-01-02', -100.00, 'Internal xfer'), 
('1103', '1102', '2014-01-04', -50.00, 'Withdrawal'); 
To find the balance in any account by some date is:
SELECT acct_nbr, SUM(trans_acct) AS current_acct_amt
  FROM Transactions 
 WHERE trans_date <= @in_some_date; 
See how simple it an be?  
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL