stored procedures – Connection server timeout – Not queried

This is just a guess, but I would try to enable the delayed schema check for the linked server under heavy load:

EXEC master.dbo.sp_serveroption @server=N'Linked_Server_name', @optname=N'lazy schema validation', @optvalue=N'true'

If this option is set to false, SQL Server checks the default value
for schema changes that have occurred since compilation in Remote
Tables. This check is done before the query runs. If anything changes
In the schema, SQL Server recompiles the query with the new schema.

When this option is set to true, schema validation is performed on remote tables
delayed until execution. This can cause a distributed query to fail
with an error if the schema of a remote table has changed between
Query creation and execution.


To check only the connection server's metadata when you query the linked server itself.

Another workaround could be to use dynamic SQL statements to query the linked server

DECLARE @SQL nvarchar(max)
IF (1=1)
N'SELECT * FROM OPENQUERY(LinkedServer,''SELECT * FROM master.sys.databases'')'

Stored Procedures – After upgrading the DB to SQL Server 2019, SP reports a "Out of Memory" error

I moved a SQL Server 2012 (8 GB) database to a newly set up SQL Server 2019 virtual machine with the same memory and CPU configuration and changed the compatibility level in SQL Server 2019. Everything in my application works fine except for a stored procedure. This consists of a large SQL query with two parameters (and no options that are not selected). When this SP is executed, the SQL Server process's memory increases to the specified maximum level and returns the error "There is not enough memory to run this query."

If I execute the SQL query (within the stored procedure) outside of it in a separate query window in SSMS, it will execute in no time and return the expected 300 lines. Even if I change the compatibility level of the database to "SQL Server 2017" and execute the stored procedure, everything is fine.

At first I thought it might be a parameter sniffing problem, but none of the workarounds worked (for example, OPTION (RECOMPILE)).

What could be the cause of the error, or did I find an error in SQL Server 2019?
Many thanks! Anne

stored procedures – Error: New transaction can not be created because the capacity has been exceeded

We receive error messages from our SQL server when we run a stored procedure to increase a counter. This SP is often executed for different entities, but when run on a GLS tracking number, we sometimes get:

"New transaction can not be created because capacity has been exceeded"

The SP is run with a separate username to exclude it from the transactions in which the user resides.

What causes this error message?

SQL Server – How to optimize stored procedures so that they do not end with Out of Memory Excetoption

I have created a stored procedure that checks against 2 and then deletes from the 3.
When I run the stored procedure in Management Studio, the exception mentioned in this question appears: StackExchange question
But what my question is how to optimize the SP so that it does not take so long to run?
My code is as follows:

 CREATE PROCEDURE (dbo).(Clean) ( 
 @Deletion date
  ) AS

DECLARE @id int
Declare @ErrorCode int =1

 DECLARE cursorE CURSOR local fast_forward FOR
        select distinct m.ID
        from Member m
        left join (
            select *, row_number() over (PARTITION BY rid order by ceid 
desc) as rn
            from TypeA
        ) x on m.ID = x.ID and x.rn = 1
        where (
            (x.ceid is null and m.LastChangedDateTime < @Deletion) 
            or x.Resignation < @Deletion

    OPEN cursorE

     WHILE ( @@FETCH_STATUS = 0 )  
  DELETE FROM Errn WHERE erid = @id
 CLOSE cursorE
-- Rollback the transaction if there were any errors
 RETURN @ErrorCode


Architecture – Microservices and Stored Procedures

There is nothing that explicitly prohibits or opposes the use of stored procedures with microservices.

Disclaimer: I do not like stored procedures from a developer's POV, but this has nothing to do with microservices.

Stored procedures usually work with a monolith database.

I think you are making a logical mistake.

Stored procedures are decreasing nowadays. Most of the stored procedures that are still in use come from an older codebase that still exists. At that time, monolithic databases were much more common than at times when microservices became popular.

Stored procs and monolithic databases both come from old codebases, so you'll see them together more often. But that is not a causal connection. They do not use stored procs there You have a monolithic database. You do not have a monolithic database there They use stored procs.

Most books on microservices recommend one database per microservice.

There is no technical reason why these smaller databases can not have stored procedures.

Like I said, I do not like stored procs. I find it awkward and resistant to future maintenance. I think that distributing sprocs to many small databases further aggravates the problems that I do not already like. That does not mean that it is not possible.

Again, most books on micro-service architecture state that they should be autonomous and loosely coupled. Integrate the microservice closely with this technology using specially stored Oracle stored procedures.

On the other hand, the same argument can be made for the ORM used by your microservice. Not every ORM supports every database. The coupling (especially its tightness) is a relative concept. It's about being as relaxed as possible.

Sprocs generally suffer from tight coupling, regardless of microservices. I would generally advise against Sprocs, but not especially because you use microservices. It's the same argument as before: I do not think sprocs are the right way (in general), but that might just be my bias, and it's not microservices.

Most MSA books (which I read) recommend that microservices should be business oriented (developed with Ddd). Moving business logic to stored procedures in the database no longer works.

That has always been my main problem with Sprocs: business logic in the database. Even if it is not the intention, it somehow always ends like this.

But even here, there is this point of criticism, regardless of whether you use microservices or not. The only reason it looks like that is that microservices are pushing you to modernize your entire architecture and that sprocs are no longer so popular in modern architectures.

Stored CRUD procedures in Oracle PL / SQL without using cursors

I have a little doubt about the procedures stored in Oracle. You asked me to do a CRUD of a table (table: position, columns: ID, name and description) using store procedures. The problem is that I have been asked for the SP not to use cursors.
My question is how I use no cursors.
If someone can show me an example, I would appreciate it very much.

Is the Korean nose correction permanent? Standard Nasal Correction Procedures – Everything Else

1. Is the Korean nose correction permanent?

Korean nose correction is one of the most popular beauty methods for the nose, especially for young people. Recently, however, a number of rhinoplasty complications have been reported in the media, which makes many people skeptical of this beauty method. So The Korean nasal augmentation is permanent?

+ Does the Korean nasal augmentation have an effect?


Korean rhinoplasty has no health effects

According to experts, Korean rhinoplasty is a simple and less invasive form of surgery that only affects the skin and soft tissue without affecting the structure and function of the nose.

In essence, Korean rhinoplasty is a method of beautifying the superior nose shape, which is capable of overcoming the condition of lower and shallow noses by applying cushioned material to improve the bridge of the nose.

Padded material used in Rhinoplasty is a kind of biological material with complete compatibility with the body to minimize the excretion Complications after surgery,


In addition, the Korean rhinoplasty is performed according to the standard procedure of the Ministry of Health, so that it can be confirmed that the answer to the question of Korean rhinoplasty is not good, because it helps you to determine the nose shape. perfect as desired.

Rhinoplasty has no effect, but why are there so many complications after a nose job? If you notice, rhinoplasty complications occur at unreliable addresses, underground activities with a team of poorly qualified doctors and unsecured facilities.

Therefore Korean nose correction goodWhich effect is no longer dependent on surgeon factor, facilities, fillers and rhinoplasty procedure. To ensure these factors, you need to find a reputable address for nose surgery.

+ Korean rhinitis rhinoplasty okay?

1555995501-3186-ce34e6283a69d3378a78.jpg "data-ratio =" 100.00 "style =" border: none; "width =" 700 "data-src =" "src =" applications / core / interface / js / spacer.png "/>

	<em>People with sinusitis may still have a normal nose job without any effect</em>
<p>	Sinusitis or allergic rhinitis are common in a wet tropical monsoon like Vietnam. For this reason, many customers who come to VietCharm for advice on rhinoplasty are asking this question.
<p>	In sinusitis, the nose can be raised as usual because the rhinoplasty only affects the skin and soft tissue without affecting the airways.
<p>	Many cases of severe sinusitis have had a minor rhinoplasty effect in VietCharm, and even some cases have improved this condition after rhinoplasty.
<p><img alt=

2. Standard nose correction procedure

In order to have a perfect and safe nose, doctors usually follow the following procedure:

  • Step 1: Visit the nose to assess the condition, identify the pros and cons of the nose, and then recommend the customer to use the appropriate nose correction method.

  • Step 2: Have customers make a general health check to see if their health status matches the operation.

  • Step 3: Next, the doctors perform measurements and drawings to shape the nose so that the surgical process becomes precise and fast.

  • Step 4: Before surgery, the surgeon will administer a light anesthetic to the client to minimize pain and anxiety during surgery.

  • Step 5: Perform the operation according to the specified instruction.

  • Step 6: Close the incision and finish the nose correction.

  • Step 7: Perform a re-examination after the operation.

Rhinoplasty is also a factor that helps you answer the question of whether the nose surgery is painful. A standard rhinoplasty that disinfects and anesthetizes before surgery helps you to feel no pain or discomfort during the procedure.

To register a high-quality rhinoplasty service at VietCharm at a reduced price, please contact us on the hotline: 0941,939,393 – 0911,688,666 for enthusiastic advice from our staff. ,

See also:

SQL Server schema of the sync database table and stored procedures

We have 2 databases, one is on our server, the other is local.
and we both need to synchronize in a way that the local database contains all the data and the server database contains no data, just empty tables and stored procedures and functions.

In the server database, we change stored procedures and functions as tables as before in the server database and the local database

Table 1 (ID, name, price)

common to both db

now we switch to the server db

Table 1 (ID, name, price, IsActive)

Where the local database still has an old structure and we can not delete the table due to data, but we want the IsActive field in the local database

and the need to synchronize stored procedures and functions.

In simple words, we need a solution to synchronize stored procedures and functions and the table schema without corrupting existing data.

can anyone suggest any tools or codes that we can use to satisfy the same
with some google and search we found a codeproject article, which can be used for fresh databases. still share the link below.

Many thanks

Stored Procedures – To update the column value based on the number of another column without an aggregate error

I'm trying to set a column value to "YES" if certain criteria are met. Some of these criteria apply when the number of column values ​​is greater than 1. Some of the criteria are not based on the number.

The goal is to mark a lgh_type3 field as Yes if a driver needs to pick up or deliver in certain areas. There are states (8) that pay a bonus, and there are three-digit zip areas that pay a bonus. The bonus is applied automatically when "Yes" is displayed in the "lgh_type3" field. I've tried different combinations within the update statement, but still get the aggregate error. The count is needed when a trip is split. This lists 2 ord_hdrnumbers in the legheader table. The same driver is displayed on both legs, and the driver's count is also indicated at 2.

ALTER procedure (dbo).(update_move_postprocessing_EastCoast) (@leg int)

declare @EC_State table (OD_State varchar (2)) --States that pay when picked or delivered in.
insert into @EC_State (OD_State) Values
('ME'), ('VT'), ('NH'), ('MA'), ('CT'), ('RI'), ('NJ'), ('DE'), ('DC'), ('MD')

declare @EC_Zip table (OD_Zip varchar(3))
insert into @EC_Zip (OD_Zip) Values

update L
set L.lgh_type3 =  
Case when Exists  
(Select ord_originstate, ord_deststate from orderheader where (ord_originstate =T.OD_State or ord_deststate = T.OD_State ))
       Then 'YES'
       Else 'NO'
from legheader L 
Inner Join @EC_State T on T.OD_State = L.lgh_startstate or T.OD_State =  L.lgh_endstate
Inner Join orderheader O on O.ord_hdrnumber = L.ord_hdrnumber
where L.ord_hdrnumber = @leg 

update L
Set L.lgh_type3 = 
 Case  when exists
       (Select count(ord_hdrnumber) , count(lgh_driver1)  from legheader where Count(ord_hdrnumber)>1 and Count(lgh_driver1)>1 and T.OD_State in(Ord_originstate,ord_deststate))
       then 'YES'
       Else 'NO'
from legheader L 
Inner Join @EC_State T on T.OD_State = L.lgh_startstate or T.OD_State =  L.lgh_endstate
Inner Join orderheader O on O.ord_hdrnumber = L.ord_hdrnumber
where L.ord_hdrnumber = @leg 

update L
set L.lgh_type3 =  
Case When Exists 
( Select Left (ord_origin_zip,3), Left (ord_dest_zip,3) from orderheader join @EC_Zip on (Left(ord_origin_zip,3) = T.OD_Zip) or (Left(ord_dest_zip,3) = T.OD_Zip))
       Then 'YES'
       Else 'NO'
from legheader L 
Inner Join @EC_Zip T on T.OD_Zip = Left (L.lgh_originzip,3) or T.OD_Zip =  Left (L.lgh_endstate,3)
Inner Join orderheader O on O.ord_hdrnumber = L.ord_hdrnumber
where L.ord_hdrnumber = @leg 

update L
Set L.lgh_type3 = 
Case When Exists
(Select count(ord_hdrnumber) ,count(lgh_driver1) from legheader where count (ord_hdrnumber)>1 and count(lgh_driver1)>1 and (Left(ord_origin_zip,3) = T.OD_Zip or LEft(ord_dest_zip,3)=T.OD_Zip))
       then 'YES'
       Else 'No'
from legheader L 
Inner Join @EC_Zip T on T.OD_Zip = Left(L.lgh_originzip,3) or T.OD_Zip =  Left(L.lgh_destzip,3)
Inner Join orderheader O on O.ord_hdrnumber = L.ord_hdrnumber
where L.ord_hdrnumber = @leg 


Grant Execute on update_move_postprocessing_EastCoast to public

For example, what happens is that a driver picks up a load in a city whose postal code starts at 196. This should set the lgh_type3 field to YES, which in turn activates a rate that pays as much per mile based on lgh_type3 = YES.