Tally Integration with SQL Server

Rapidinfologix Professional release supports import of information from SQL Server database to Tally ERP 9. It underpins :

All adaptations of SQL Server

Count 6.3 and higher adaptations

Beginning

How would I move information from SQL Server database into Tally?

Before we continue, how about we have take a gander at the means engaged with Excel to Tally versus SQL Server to Tally.

Steps Import from Excel to Tally Import from SQL Server to Tally Remarks

Step 1 Start udiMagic Software Start udiMagic Software

Step 2 Select alternative Excel to Tally Select choice Advanced Usage

Step 3 Select alternative Import information into Tally Select choice MS-SQL Server [SQL Server to Tally]

TODO : Specify the Configuration string to interface with the SQL Server database

Step 4 Select the Excel file Select the Query document

[Excel to tally]

Select any Standard Excel layout furnished with udiMagic Software. Model: Vouchers-Sales-Purchase-Basic.xls

[SQL Server to Tally]

TODO : Write SQL SELECT articulation to recover information from your database tables. Your SELECT question should restore indistinguishable segments from given in the Standard Excel layout.

Step 5 Select the XML document

[Optional - XML document is consequently selected] Select the XML record

[Mandatory] Each Standard Excel layout furnished with udiMagic has a relating XML record.

Here's a model:

Exceed expectations document: Vouchers-Sales-Purchase-Basic.xls

XML document : Vouchers-Sales-Purchase-Basic-xml-tags.xml

Step 6 Click the Start button Click the Start catch

As it tends to be seen, the above errand to import from SQL Server to Tally includes two fundamental things:-

To compose Connection String to associate with SQL Server

To compose SQL-SELECT explanations to bring information from the SQL Server database

Alert

Tally Integration Despite the fact that utilization of udiMagic does not require any programming information, you need comprehension of SQL (Structured inquiry Language). What's more, obviously, you should have the rights/benefits to get to the SQL Server database.

Composing Connection String

Pursue these means :-

Tally Service Provider

Next, select Advanced Usage choice.

Next, select the Database-type as SQL Server

Next, click on the Settings catch and determine the "association string" for your SQL Server.

Next, click on the TEST SERVER CONNECTION catch to test-check the association.

Notes:

A Connection string is a string that contains data required to associate with a database or an information document. Since there are a few suppliers and every supplier may have various approaches to make an association, you can compose an association string in different ways.

An association string comprises of arrangement of catchphrase worth sets isolated by semicolons (;).

The equivalent to sign (=) interfaces every watchword and its worth.

Model: Key1=Value1; Key2=Value2; key3=Value3;

Test Connection strings for associating with SQL-Server

Interfacing with a SQL Server Instance

Provider=sqloledb;Data Source=myServerName\theInstanceName;Initial Catalog=myDataBase;Integrated Security=SSPI;

Standard Security

Provider=sqloledb;Data Source=myServerAddress; Initial Catalog=myDataBase;UserId=myUsername;Password=myPassword;

Confided in Connection

Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;

Comments:-

a) You have to supplant the featured content with real qualities.

b) For more data on association strings, if it's not too much trouble allude this connection http://www.connectionstrings.com

Composing SQL-SELECT explanations

As database structures change from case to case, you should compose SQL articulations (questions) to get information from SQL Server.

Test SQL SELECT question

<SQL.LIST>

<SQL>SELECT vchno as id,basevtype,vchtype,vchno,vchdate,refno,refdate,partyname,partygstin,statename,itemname,hsncode,uom,qty,rate,discount,amount,igstrate,igstamt,cgstrate,cgstamt,sgstrate,sgstamt,salepurcledger,igstledger,cgstledger,sgstledger,narration FROM gstdata</SQL>

</SQL.LIST>

Comments:

a) You should compose SQL SELECT to choose fitting fields from your database tables.

b) Save the SQL Query in a record with expansion qry.

c) If required, if it's not too much trouble counsel your framework manager to compose SQL SELECT articulation.

Extra notes:

SQL-inquiries are commonly written in a Text document (having .qry augmentation). You can utilize any TEXT-editorial manager (like Notepad) to see/alter the SQL-inquiry records. udiMagic enables you to compose various SQL-SELECT explanations in a Query (qry) document. As should be obvious, each SQL-SELECT articulation is to be encased in <SQL>....</SQL> tag. This enables you to have various questions in a solitary Query (txt) document. udiMagic forms these inquiries one-by-one in the request in which they show up in the question document. It contructs an outcome informational index which can be pictured as Columnar arrangement involving Rows and Columns. The primary field in the outcome informational collection can be gotten to utilizing COLUMNREFERNCE A, the second field in the outcome informational collection can be gotten to utilizing COLUMNREFERENCE B, etc.

Bringing in information from SQL Server to Tally

Begin Tally Software 

Select the choice Advanced Usage

Select the choice SQL Server

Snap the Browse catch and select the "SQL Query record"

Snap the Browse catch and select the "XML record"

Snap the Start catch