The code that I sent from asp.net as a new batch slows down slow new database using 17000 lines of script I am facing a problem with the creation. The problem with an order is that execution of this script sometimes takes more than 20 during peak times. If I run this script in SQL Server Management Studio, then it takes 2S.
What is the best practice to build a database on request, DB by scripting an archived procedure, database cloning, pre-creation and renaming it? We need to ensure that it is compatible under load under concurrent environment.
Thank you.
17000 lines on the wire on a SQL server seem like a terrible quantity and as slow as possible is. So, using ASP.NET's SQL client to do something like that.
Yes, I am in your favor using a stored procedure to do this. DB is also not sure about cloning and renaming operations; I can bet you can be away from defining it by using parameters in your stored procedure.
No comments:
Post a Comment