I developed a website using Asp.Net MVC and Edmx database and I published this website on azure and my database is also on azure and I've a functionality on website that uploads excel record into database and that excel sheet contain almost 18000 records every time I upload that sheet it throw Timeout error after some time so what should I do.

[![enter image description here](https://i.stack.imgur.com/n32VE.png)](https://i.stack.imgur.com/n32VE.png)

Initially I was not using any command Timeout but after doing some research I'm using this in constructor 

```
 public ProfessionalServicesEntities()
        : base("name=ProfessionalServicesEntities")
    {
        this.Database.CommandTimeout = 10000;
        //this.Database.CommandTimeout = 0; //I tried this too.

        //((IObjectContextAdapter)this).ObjectContext.CommandTimeout = 3600;
    }

```

Here is the code of
function :-

```
 public void SaveEquipments(IEnumerable<EquipSampleEntity> collection)
    {
        using (ProfessionalServicesEntities db = new ProfessionalServicesEntities())
        {
            string modelXml = XmlSerialization.ListToXml(collection.Where(x=>x.Type == Model).ToList());
            string accessoryXml = XmlSerialization.ListToXml(collection.Where(x => x.Type == Accessory).ToList());
            db.ImportEquipmentFile(modelXml, accessoryXml);
        }
    }

```

here is context file code for SP:-

```
 public virtual int ImportEquipmentFile(string modelXml, string accessoryXml)
    {
        var modelXmlParameter = modelXml != null ?
            new ObjectParameter("ModelXml", modelXml) :
            new ObjectParameter("ModelXml", typeof(string));

        var accessoryXmlParameter = accessoryXml != null ?
            new ObjectParameter("AccessoryXml", accessoryXml) :
            new ObjectParameter("AccessoryXml", typeof(string));

        return ((IObjectContextAdapter)this).ObjectContext.ExecuteFunction("ImportEquipmentFile", modelXmlParameter, accessoryXmlParameter);
    }

```
['https://Stackoverflow.com/questions/45320053', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/4207036/']
I actually Solved my problem. I did everything correct. But only thing I did not do is to map the hostname with the same ip in Route53. And instead of accessing the website with hostname, I was accessing it from IP. Now after accessing the website from hostname, I was able to access it :)
Seems like you posted [here and got your answer](https://github.com/nginxinc/kubernetes-ingress/issues/76). The solution is to deploy a different Ingress for each namespace. However, deploying 2 Ingresses complicates matters because one instance has to run on a non-standard port (eg. 8080, 8443).

I think this is better solved using DNS. Create the CNAME records `cafe-qa.example.com` and `cafe-dev.example.com` both pointing to `cafe.example.com`. Update each Ingress manifest accordingly. Using DNS is somewhat the standard way to separate the Dev/QA/Prod environments.