Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Non Business Central tables in BC database
uri84
Member Posts: 30
Hi,
Someone knows if having non BC tables in the database and use them via SQL stored procedure to save additional info can affect to the Business Central performance and locks?
The scenario is that, just as there are tables like "dbo.CompanyName.Table," there are other tables created, such as info.OrderLog, and many of these tables, which are external to Business Central, have different stored procedures triggered by the SQL Agent in the same Business Central database. Could this approach affect the performance of Business Central? I have observed a lock in the database of one of the stored procedures waiting for a standard select on the customer table to finish.
I know that this is not a best practice, but i need to know if something could happen...
Thanks!
Someone knows if having non BC tables in the database and use them via SQL stored procedure to save additional info can affect to the Business Central performance and locks?
The scenario is that, just as there are tables like "dbo.CompanyName.Table," there are other tables created, such as info.OrderLog, and many of these tables, which are external to Business Central, have different stored procedures triggered by the SQL Agent in the same Business Central database. Could this approach affect the performance of Business Central? I have observed a lock in the database of one of the stored procedures waiting for a standard select on the customer table to finish.
I know that this is not a best practice, but i need to know if something could happen...
Thanks!
0