#iec code modification

[financialsolution]

Online Registration for Import Export Code (IEC) The Import & Export Code, or IEC number, is a commonly used designation. The Directorate General of Foreign Trade issues the ten-digit Import & Export Code (DGFT).

A business that engages in import and export must possess an IEC registration certificate.

What is import export code? A crucial corporate identification number called an import-export code (IEC) is necessary for all foreign trade in India. IEC Code is valid for life, and if any details change, IEC Code modifications can be made in accordance with such changes.

[kanakkupillai-trademark]

How to Modify or Update Your IEC (Import Export Code) Registration Details

The Import Export Code (IEC) is essential for any business in India engaged in importing or exporting goods and services. Issued by the Directorate General of Foreign Trade (DGFT), IEC registration is a mandatory license for international business transactions. Occasionally, businesses may need to update or modify their IEC registration details due to changes in address, contact information, business structure, or other vital elements. Here’s a guide to help you understand the process for effectively updating or modifying your IEC registration details.

Why Update Your IEC Registration Details?

Keeping your IEC registration details current is crucial for several reasons:

Compliance: Incorrect information can lead to non-compliance with government regulations.

Seamless Transactions: Updated information ensures smooth customs clearance and compliance with foreign trade laws.

Avoid Penalties: Not updating IEC details promptly may attract penalties or create complications with the DGFT.

When Should You Update Your IEC Registration?

You may need to modify your IEC registration details in the following situations:

Change of Address: When your business address has changed.

Change in Business Name: If there’s a rebranding or alteration in your registered business name.

Updating Contact Details: To reflect changes in phone numbers, email addresses, or other contact information.

Change in Business Structure: If you change the structure of your business, such as converting a sole proprietorship into a private limited company.

Modifying Bank Account Details: If you change your business bank account, which is used for international transactions.

Changes in Directors or Partners: When there is an addition or removal of directors or partners in the business.

Steps to Update Your IEC Registration Details

Updating or modifying your IEC registration is a straightforward online process. Here’s a step-by-step guide:

Step 1: Visit the DGFT Portal

Go to the official DGFT (Directorate General of Foreign Trade) portal: https://www.dgft.gov.in/.

Log in using your credentials, including the registered User ID and Password. If needed, you may also use your Digital Signature Certificate (DSC) or Aadhaar-based OTP.

Step 2: Access the IEC Dashboard

Once logged in, navigate to the IEC dashboard.

Here, select the option to Modify/Update IEC.

Step 3: Edit the Necessary Fields

In the modification section, update the details that need to be changed, such as business address, contact information, business structure, etc.

Upload the required documents to support the changes. These may include:

Updated address proof (lease agreement, utility bills, etc.)

Bank certificate or cancelled cheque if updating bank details

Director/partner details in case of a change in business structure or composition

Relevant board resolution or partnership deed

Step 4: Pay the Modification Fee

Once the details are updated, pay the modification fee as required by the DGFT. The fee structure may vary, so it’s advisable to check the latest charges on the DGFT portal.

Payments can be made online using net banking, credit card, or debit card options available on the portal.

Step 5: Submit the Application

After entering the updated information and paying the fee, submit your application.

You will receive an application number for tracking purposes. The DGFT will review the changes and, upon verification, approve them.

Step 6: Receive the Updated IEC Certificate

Once approved, the updated IEC certificate will be available in your DGFT account dashboard. You can download and print it for your records.

Documents Required for IEC Modification

The required documents may vary based on the type of modification but generally include:

Updated Address Proof: Lease agreement, utility bills, or property ownership proof for address updates.

Bank Account Details: A cancelled cheque or bank certificate if updating bank account information.

Business Structure Documents: Board resolution, partnership deed, or memorandum of association (MOA) if there’s a change in business structure.

Director/Partner Identity Proof: Updated ID proof for any changes in directors or partners.

Important Points to Remember

Annual IEC Update: As per the latest DGFT guidelines, IEC holders must update their IEC details on the DGFT portal annually between April and June, even if no changes have been made. Failure to do so may render the IEC inactive.

Accurate Documentation: Ensure that the supporting documents you upload are precise and straightforward to avoid delays in the modification process.

Monitor Approval Status: On the DGFT portal, use your application number to track the status of your modification application.

Conclusion

Updating your IEC registration details is crucial for business compliance and smooth international transactions. By following the steps above, you can efficiently handle any modifications to your IEC information through the DGFT portal. Ensure timely updates to avoid disruptions in your import-export operations and stay compliant with DGFT regulations.

[isocertificationinfrance]

A Complete Guide to Safeguarding Personally Identifiable Information (PII) in Public Cloud Services: ISO 27018 Certification

ISO 27018 Certification in Bangalore:The quick development of cloud computing in the current digital era has completely changed how businesses handle and keep data. But these developments also bring with them a host of new difficulties and worries, chief among them the security and privacy of personal information. An international standard called ISO 27018 provides rules for safeguarding personal information stored in the cloud, therefore addressing these issues. The complexity of ISO 27018 certification is examined in detail in this article, together with its significance, advantages, application procedure, and function in guaranteeing cloud data security.

ISO 27018: What is it?

The international standard ISO 27018, "Information technology — Security techniques — Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors," was created by the International Organisation for Standardisation (ISO). 2014 saw the publication of It expands upon the foundation of ISO/IEC 27001, which describes the specifications for an information security management system (ISMS), and ISO/IEC 27002, which is a generally accepted standard for information security management.

The security of personally identifiable information (PII) in the cloud is the special emphasis of ISO 27018. It offers cloud service providers (CSPs) that handle personal data on behalf of their clients a thorough set of safeguards and best practices. The standard makes sure that PII is managed in accordance with relevant data protection rules and regulations, which attempts to improve accountability, transparency, and confidence in cloud computing settings.

The Fundamentals of ISO 27018

PII in cloud systems is protected by ISO 27018 Consultants in Bangalore, which is founded on a number of important concepts. Among these guidelines are:

Consent and Choice: Before collecting, using, or disclosing PII about data subjects, cloud service providers are required to have their express consent. They should also provide people easy ways to control the data that interests them.

Limitation of Use: Personally Identifiable Information (PII) shall only be used for explicit, authorized reasons that have been informed to data subjects. Additional permission is required for any secondary use of the data.

Data Minimization: Cloud service providers should only gather and hold onto the bare minimum of personally identifiable information (PII) required to achieve the stated goals. Data that is not needed should be anonymised or erased.

Accuracy: Entities are required to take appropriate measures to guarantee that the PII they handle is precise, comprehensive, and current. It should be possible for data subjects to fix errors.

Security: To guard against unauthorized access, disclosure, modification, or destruction of PII, appropriate organizational and technical safeguards must be put in place.

Accountability: It is the duty of cloud service providers to prove that they are in conformity with ISO 27018 standards. They must keep documentation of their data security procedures and carry out frequent audits.

The Significance of Certification in ISO 27018

Achieving ISO 27018 Services in Bangalore  has several advantages for CSPs and their customers. The following are some of the main benefits:

Enhanced Self-Belief and Trust:

A CSP's dedication to safeguarding personal information and upholding international standards is demonstrated by their ISO 27018 certification.

Clients, partners, and stakeholders gain confidence and trust as a result.

Advantage of Competition:

The ISO 27018 certification may make a big difference in a crowded market.

By demonstrating to prospective customers that a CSP values data security and privacy, it may draw in more business.

Adherence to Regulations:

CSPs may better link their data protection procedures with relevant laws and regulations, such the General Data Protection Regulation (GDPR), by using ISO 27018.

This lowers the possibility of fines and improves adherence to international data criteria for protection.

Enhanced Risk Handling

The standard offers a methodical way to recognise and lessen risks related to processing personally identifiable information.

This lowers the possibility of data breaches and mishaps and results in stronger security procedures.

Efficiency of Operations:

By putting ISO 27018 recommendations into practice, operational efficiency may be increased and data protection procedures can be streamlined.

It promotes a security and privacy conscious culture inside the company.

The Procedure for Certification

There are several phases involved in obtaining ISO 27018 certification, and each one needs to be carefully planned and carried out. An outline of the certification procedure is provided here:

Analysis of the Gap:

Examine the organization's current data protection procedures in detail in comparison to ISO 27018 regulations.

Determine which areas require improvement in order to comply with the controls of the standard.

Execution:

To close the holes found, create and execute policies, processes, and controls.

This might entail improving data governance procedures, modernizing security mechanisms, and educating employees on data protection best practices.

Internal Exam

Conduct an internal audit to verify ISO 27018 Implementation in Bangalore compliance and assess how well the controls have been applied.

Take care of any problems or non-conformities found during the audit.

Audit for Certification:

Hire a recognised certifying authority to carry out an outside assessment.The certifying authority will evaluate the company's adherence to ISO 27018 and confirm that the controls are being applied correctly.

Maintenance and Certification:

The organization will receive ISO 27018 certification if all standards are met.

To keep certification current and guarantee continued compliance, regular surveillance checks and CPD initiatives are crucial.

Guide to Achieving  ISO 27018 Certification :

ISO 27018 Certification Consultants in Bangalore  guarantees that goods are consistently produced and managed in compliance with quality standards. Product safety and efficacy are vital in sectors including food, cosmetics, and medicines. The term "B2B CERT" most likely refers to a certification body or process intended for business-to-business transactions that shows supply chains' conformance to ISO 27018 standards. With partners, this accreditation establishes confidence and trust by proving a dedication to quality and compliance. 

[gulshan-123]

Best services  to register IEC in same days

"IEC" stands for Importer Exporter Code, a 10-digit alphanumeric code issued by the Directorate General of Foreign Trade in India. It's a unique identifier required for engaging in import and export activities.

[saspowertechsblog]

short circuit analysis services

Importance of Short circuit analysis services

Short circuit analysis is a process of calculating the maximum amount of electrical current that can flow through a given circuit under a fault condition, such as a short circuit. A short circuit occurs when an unintended connection is made between two points in an electrical circuit with low resistance, causing a high current to flow.

The purpose of performing a short circuit analysis is to determine the magnitude of the current that would flow during a fault condition, which is critical for designing and selecting protective devices such as circuit breakers and fuses. The analysis also helps to identify potential hazards and vulnerabilities in the system, which can be addressed to improve the safety and reliability of the electrical system.

The short circuit analysis typically involves calculating the fault current magnitude, determining the fault current path, and analysing the performance of protective devices under the fault conditions. This information can be used to identify potential areas of concern and to select appropriate protective devices that can isolate the faulted section of the system and prevent damage to the equipment and harm to people.

Why is Short circuit analysis performed?

Short circuit analysis is performed for several reasons, including:

To determine the maximum current that could flow during a fault condition: This is important because excessive current can cause equipment damage, fires, and other hazards. By knowing the maximum current that could flow during a fault, engineers can select the appropriate protective devices, such as fuses or circuit breakers, to prevent excessive current from flowing.

To identify potential hazards: Short circuits can create hazards such as electric shocks, electrical fires, and explosions. By identifying potential short circuit hazards in advance, engineers can take appropriate measures to prevent them from occurring or mitigating their impact.

To comply with industry standards and regulations: Short circuit analysis is required by various industry standards and regulations, such as the National Electric Code (NEC) and the International Electrotechnical Commission (IEC), to ensure the safety and reliability of electrical systems.

To optimise the design of the electrical system: Short circuit analysis can help engineers to optimise the design of an electrical system by identifying areas of the system that may require additional protective devices or modifications to prevent potential faults from occurring.

Performing a short circuit analysis is essential for ensuring the safety and reliability of electrical systems, complying with industry standards and regulations, and optimising the design of an electrical system.

Different types of Short circuit analysis services

There are different types of short circuit analysis services that are typically offered by electrical engineering firms, consultants, and contractors. Some of these services include:

Arc flash hazard analysis: This type of short circuit analysis is focused on identifying the hazards associated with an arc flash event, which is a type of electrical explosion that can occur during a short circuit. An arc flash hazard analysis includes calculating the incident energy level, determining the arc flash boundary, and identifying appropriate personal protective equipment (PPE) for workers.

Fault current analysis: This type of short circuit analysis is focused on calculating the maximum current that could flow during a fault condition, which is critical for selecting the appropriate protective devices such as circuit breakers and fuses. Fault current analysis typically involves using computer modelling software to simulate the behaviour of the electrical system under fault conditions.

Coordination study: This type of short circuit analysis is focused on ensuring that protective devices, such as circuit breakers and fuses, are coordinated properly to isolate faults and minimise the impact on the electrical system. Coordination studies typically involve analysing the time-current characteristics of protective devices to ensure that downstream devices trip before upstream devices.

Load flow analysis: This type of short circuit analysis is focused on analysing the flow of power in the electrical system under normal operating conditions. Load flow analysis is typically used to determine the capacity of the electrical system, identify potential areas of overload, and optimise the design of the system.

The different types of short circuit analysis services are offered to address different aspects of the electrical system, including fault current analysis, arc flash hazard analysis, coordination study, and load flow analysis.

Importance of Short circuit analysis services

Short circuit analysis services are essential for ensuring the safety, reliability, and efficiency of electrical systems. Here are some of the key reasons why short circuit analysis services are important:

Safety: Short circuit analysis services help identify potential hazards associated with electrical faults, such as electric shocks, fires, and explosions. By identifying potential hazards in advance, measures can be taken to prevent or mitigate their impact, reducing the risk of injury or damage to equipment.

Compliance: Short circuit analysis services are often required by industry standards and regulations, such as the National Electric Code (NEC) and the International Electrotechnical Commission (IEC), to ensure that electrical systems are safe and reliable.

Efficiency: Short circuit analysis services can help optimise the design of electrical systems by identifying areas of the system that may require additional protective devices or modifications to prevent potential faults from occurring. This can help reduce downtime and maintenance costs, as well as increase the overall efficiency of the system.

Cost savings: Short circuit analysis services can help identify potential areas of overload, which can lead to equipment failure and downtime. By identifying and mitigating potential overloads, costly downtime and repairs can be avoided.

Liability: Failure to perform short circuit analysis services can expose businesses to potential liability in the event of an accident or injury resulting from electrical faults.

The Short circuit analysis services are important for ensuring the safety, reliability, and efficiency of electrical systems, as well as compliance with industry standards and regulations. These services can help identify potential hazards, optimise system design, and reduce downtime and maintenance costs, ultimately leading to cost savings and reduced liability.

Conclusion

Short circuit analysis services are essential for ensuring the safety, compliance, efficiency, cost savings, and reduced liability of electrical systems. It is important to work with qualified and experienced professionals to perform these services and to regularly review and update short circuit analysis reports to ensure that electrical systems remain safe and reliable.

[estartup2017]

Only 1 AD Code Registration for all ports.

The latest notice from DGFT regarding the high demand by traders for AD Code Registration has been issued. This update is also claimed to be beneficial for traders. It also promises that it will streamline trade and facilitate the process. Only one AD Code Registration is required for all ports according to the latest update by DGFT. This article will explain the most recent update from DGFT regarding AD Code Registration.

What is AD Code Registration?

An Authorized Dealer Code (AD) is a 14-digit number.

Two registrations are required to launch an Indian import or export business. IEC registration and AD code registration are two.

Registering for an AD Code is Important

You must register your AD Code to get customs clearance for products you import or export.

The purpose of AD Code Registration

The AD Code is designed to verify that foreign currency transactions in an exporter’s current account are legitimate.

The Custom Clearance Process:

A unique AD Code registration for each port is required in order to clear customs on goods being imported or exported.

An IEC could file a document, such as a shipping invoice, at any Customs EDI port. The registration of an AD Code and the associated bank account was a once-off transaction.

An AD Code must be registered at every port where papers are lodged. Multiple AD codes could be connected to the same IEC at different ports.

You can submit your registration request online with an ICEGATE ID, or in person at Customs House.

The IEC had to approve the registration of the new AD Code Registration at each port where it was requested.

All ports only 1 AD Code registration

Before being accessible at all customs websites, the AD code and linked bank account must be registered at one port. Any update or registration of a new AD Code at any port must take place online at ICEGATE.

The "CLK" role in ICES has prevented the ability to add or change the AD code or account against an IEC. The application would be approved by the CLK officer at the port, just as in the current process.

After it is registered against an IEC, an AD code can be used at any port. Additional registrations are not required at any other ports.

Any modification to AD code account information must also be done at the port of registration that was designated by IEC at the time the registration application was submitted. A registered IEC can have multiple AD codes and related accounts. This aspect has not changed.

As instructed, all multiple AD codes must register in the system at one port. Multiple registration ports are available for different AD codes for an IEC.

Register for an AD Code Update

For any existing AD codes and associated accounts registered to an IEC, it is the Customs port at which the latest Shipping Bill containing the AD code was filed that will be considered the port for registration of the AD code in the System. The ICEGATE login ID section's Bank Account section will show the port of registration for each AD code registered against an IEC Code Registry.

[prasad-corpaid-blog]

Get Amendment/Modifications/Change Of Address in Your Existing IEC Certificate Within 1 Hr. Complete Online Process. Expert CA/CS team Support. Change/Update Details in IEC. Call us on 9112230621/22 https://www.ieconline.in/update-iec

[seocaonweb-blog]

Import Export Code Registration: A Key Step for Your Business Expansion

In today’s globalized world, expanding your business beyond borders is a profitable opportunity. However, to engage in international trade legally, you need an Import Export Code (IEC). Caonweb will guide you through the process of IEC code registration, highlighting the significance of this vital document for your business growth.

In this article, we will delve into the significance of IEC code registration, its benefits, and how to obtain it conveniently.

Table of Contents

About Import Export Code (IEC)

Where is IEC applicable?

Where Import-Export Code Registration. is not applicable.

Documents required for IEC (Import Export Code) Registration.

Steps in the process of IEC (Import/Export Code) Registration.

Benefits of taking IEC (Import Export Code) Registration

Expert Insights

FAQs

Conclusion

Conditions where IEC is applicable?

1-At the time of customs clearance of goods by Importer IEC is required by customs authorities.

2- At the time of sending his goods by exporter IEC is required by the customs port.

3- At the time of sending money abroad through banks IEC is required by the bank.

4- At the time of receiving money in foreign currency directly into his bank account then IEC is required by the bank.

Conditions where IEC is not applicable?

IEC is not mandatory for all GST-Registered traders. PAN can be used as a new IEC code for import/export purposes. No IEC is required for personal use, government departments, ministries, and notified charitable institutions.

Steps involved in IEC (Import/Export Code) Registration

To register IEC, visit the DGFT website.

Go to the ‘Services’ tab on the homepage.

Select the ‘IEC Profile Management’ from the drop-down list.

Select the ‘Apply for IEC’ option.

Click on the ‘Register’ option. Fill in the required details and click the ‘Sent OTP’ button.

Insert OTP and register by clicking the ‘Register’ button.

After validating the OTP successfully, you will receive a temporary password, which can be further changed after logging into the DGFT website.

After registering on the DGFT website, login to the website by entering the username and password.

Go to the ‘Apply for IEC’ option on the DGFT website.

Click on the ‘Start Fresh Application’ button.

Enter the general information, details of proprietor/partner/director/Karta/managing trustee, bank information, and other details, attach a Digital Signature Certificate (DSC) and make the payment.

After successful payment, it will be redirected to the DGFT website. The receipt will be displayed. Download the receipt for future reference.

The IEC Certificate is sent via email. It can be downloaded after logging in to the DGFT website and clicking the ‘Print IEC’ option under the ‘IEC Profile Management’.

List of documents required for IEC (Import Export Code) Registration

Individuals, firms, or company’s copy of PAN Card.

Provide a copy of the proprietor’s Aadhaar card, voter ID, or passport.

Proof of establishment, incorporation or registration of the partnership, society, proprietorship firm, Pvt. company, HUF, etc. 

Proof of address of business premises, such as sale deed, lease deed, rent agreement or utility bills (electricity bill, telephone bill or mobile bill).

Enclose copies of current bank account cancellation cheques for individuals, companies or firms.

Also provide a self-addressed envelope for delivery of the IEC certificate by registered post.

Benefits of IEC registration

1-Expansion of business

IEC helps businesses expand globally and grow with their services/products.

2-Availing several benefits

The IEC registration enables companies to avail benefits for their imports/exports from DGFT, Export Promotion Council, Customs, etc.

3-No return filing

IEC registration does not require any return filings of export / Import transactions, there is no requirement to file returns with DGFT.

4-Easy processing

Obtaining an IEC code from the DGFT is a straightforward process that doesn’t require any proof of export or import. The application can be submitted and the IEC code can be obtained within 10 to 15 days.

Expert Insights: CA Sakshi Agarwal

When it comes to the intricacies of IEC code registration and its implications for your business, CA Sakshi Agarwal, a seasoned professional in international taxation and cross-border business, shares her insights and expertise to help you navigate the registration process effortlessly.

Why Caonweb is Your Trusted Business Name

For a seamless IEC code registration experience, Noida-based Tax consultants “Caonweb” stands out as a reliable and trustworthy name in the industry. Under the guidance of our expert team and a client-centric approach, we ensure the registration process is not only efficient but also compliant with all legal norms.

Frequently Asked Questions

Q1. What is the IEC code?

The IEC code, or Import-Export Code, is a 10-digit identification number required for businesses engaged in international trade.

Q2. How can I apply for an IEC code online?

You can apply for an IEC code online through the DGFT’s website by providing the necessary documents and details.

Q3. What are the benefits of having an IEC code?

Having an IEC code allows your business to engage in international trade, ensures legal compliance, and provides access to government incentives.

Q4. How long does it take to obtain an IEC code?

Typically, an IEC code is issued within 1-2 working days of applying online.

Q5. Why choose Caonweb for IEC code registration?

Caonweb is a trusted business name known for its expert guidance and client-centric approach, ensuring a smooth and compliant registration process.

Conclusion

In conclusion, the Import Export Code (IEC) is a crucial requirement for businesses looking to engage in international trade. Its benefits are numerous, and with the convenience of online registration and expert guidance from CA Sakshi Agarwal, obtaining your IEC code has never been easier. Choose Caonweb for a seamless experience and take the first step towards expanding your business globally.

In this article, we’ve covered the essentials of IEC code registration, from its significance to the online application process and the benefits it offers. With expert insights from CA Sakshi Agarwal and the trusted assistance of Caonweb, you can confidently pursue your international business ventures. Don’t miss out on the opportunities that global trade has to offer. Get your IEC code today and unlock a world of possibilities.

SOURCE: THE POST IMPORT EXPORT CODE APPEARED FIRST ON Import Export Code Registration: A Key Step for Your Business Expansion

[aishwakirti-blog]

[jencypiter-blog]

Update Import Export Code Registration

Get Amendment/Modifications/Change Of Address in Your Existing IEC Certificate Within 1 Hr. Complete Online Process. Expert CA/CS team Support. Change/Update Details in IEC.

Phone No. +91 91122 30621, +91 91122 30622

Email : support@ieconline.in

[ariashen]

V19-G-10M-PUR-ABG INGKE Female cordset single-ended M12 straight A-coded, 8-pin, PUR cable grey

Alternative/Sbustitute

Manufacturer: INGKE

Part Number: V19-G-10M-PUR-ABG

Connection:socket

Construction type:M12

Style:straight

Locking:screw connection

Number of pins:8

Coding:A-coded

Operating voltage:max. 30 V AC/DC

Operating current:max. 2 A

Degree of protection:EN 60529

Plug connection:connector M12 x 1 : IEC 61076-2-101

Plug connector:-40 ... 90 °C (-40 ... 194 °F)

Cable, fixed:-40 ... 80 °C (-40 ... 176 °F)

Cable, flexing:-20 ... 80 °C (-4 ... 176 °F)

Tightening torque:0.6 Nm

Loosening protection:available

Tool installation:straight knurling

Mating cycles:min. 100

Shielding:shield connected to screw connection

INGKE also produce substitute such as:

V1S-W-BK  V31S-GM  V3S-GM  V1-W-PG9  V1-G-PG9  V1S-G-PG9  V15S-G-PG9  V1S-K-M16P-50  V1S-K-PG13,5P-ASI  V1D-M16-V1D  V15SL-M16-500  V15L-M16-500  V1-PG13,5-Y124355  M20-V1-G-S-.3M......

INGKE Technology(www.ingketech.net) specializes in producing 100/1000/2.5G/5G/10G Base-T (with POE/POE+, 30w,60w,90w, 720mA,900mA) RJ45 connector & Circular Connectors(M5,M8,M12) ,since its establishment 1993, with technology as dependence and the market as direction,we have developed to be a competitive high-tech enterprise and a leading  manufacturer of connectors.Partnered with the global leaders in these markets, we continue to develop new products to enable high-speed communication. Now we have passed the ISO14001 Environment Management System certification and our parts are all ROHS,CE,UL and SGS parts.

INGKE Main products:

1).100/1000/2.5G/5G/10G Base-T (with POE/POE+, 30w,60w,90w, 720mA,900mA) RJ45 connector cross Pulse,Halo,Belfuse,Wurth,TE,Molex,Amphenol ...

2).Circular Connectors(M5,M8,M12) compatible with TE,NorComp,ODU,HOLIN,LEMO,Amphenol LTW,Lumberg Automation,

Phoenix contacts, CONEC,Hirose, Bulgin ,Pepperl+Fuchs...

3).We can offer OEM & ODM services and mould modification according your requirements.

aria.ingke(at)gmail.com

[moneycafe]

DGFT services on trader code, Aadhaar link to remain suspended from June 1-6

DGFT services on trader code, Aadhaar link to remain suspended from June 1-6

The government on Wednesday said that services of the Directorate General of Foreign Trade such as application for a new importer-exporter code (IEC), modification applications and one-time linking of Aadhaar for e-sign purposes will not be available from June 1-6 due to non-availability of PAN Validation Services. “In reference to the Press release by Central Board of Direct Taxes on “Launch of…

[globalmediacampaign]

Amazon Aurora PostgreSQL parameters, Part 4: ANSI compatibility options

Organizations today have a strategy to migrate from traditional databases and as they plan their migration, they don’t want to compromise on performance, availability, and security features. Amazon Aurora is a cloud native relational database service that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. The PostgreSQL-compatible edition of Aurora delivers up to 3X the throughput of standard PostgreSQL running on the same hardware, enabling existing PostgreSQL applications and tools to run without requiring modification. The combination of PostgreSQL compatibility with Aurora enterprise database capabilities provides an ideal target for commercial database migrations. Aurora PostgreSQL has enhancements at the engine level which improves the performance for high concurrent OLTP workload, and also helps bridge the feature gap between commercial engines and open-source engines. While the default parameter settings for Aurora PostgreSQL are good for most of the workloads, customers who migrate their workloads from commercial engines may need to tune some of the parameters according to performance and other non-functional requirements. Even for workloads which are migrated from PostgreSQL to Aurora PostgreSQL, we may need to relook at some of the parameter settings because of architectural differences and engine level optimizations. In this four part series, we explain parameters specific to Aurora PostgreSQL. We also delve into certain PostgreSQL database parameters that apply to Aurora PostgreSQL, how they behave differently, and how to set these parameters to leverage or control additional features in Aurora PostgreSQL. In part one of this series, we discussed the instance memory-related parameters and Query Plan Management parameters that can help you tune Amazon Aurora PostgreSQL. In part two, we discussed parameters related to replication, security, and logging. We covered Aurora PostgreSQL optimizer parameters in part three which can improve performance of queries. In this part, we will cover parameters which can align Aurora PostgreSQL closer to American National Standards Institute (ANSI) standards and reduce the migration effort when migrating from commercial engines. The ANSI has approved committees of standards developing organizations that publish best practices and standards for database query languages. Most vendors modify SQL to meet their needs and generally base their programs off the current version of this standard. The international standard (now ISO/IEC 9075) has been revised periodically ever since the first in 1986 and most recently in 2016. The PostgreSQL community tries to maintain compatibility with ANSI SQL. But some PostgreSQL behaviors don’t exactly comply with ANSI specifications. In other cases, although PostgreSQL complies with ANSI specifications, the syntax accepted by PostgreSQL is slightly different from commercial engines. Several customers, especially ISVs, strive to keep their code ANSI compatible so as to allow for DB engine independence for their product or offering. Amazon Aurora PostgreSQL adds additional capabilities that can be helpful for retaining behavior when migrating from other databases, such as Oracle or Microsoft SQL Server. These features were introduced in Aurora PostgreSQL 3.1.0 (compatible with PostgreSQL 11.6) and Aurora PostgreSQL 2.4.0 (compatible with PostgreSQL v10.11) and are controlled by additional parameters. These features are also available in newer major versions release such as Aurora PostgreSQL 4.x (compatible with PostgreSQL 12). In this post, we cover parameters that control these compatibility behaviors in Aurora PostgreSQL. ansi_constraint_trigger_ordering This parameter controls whether Aurora PostgreSQL retains PostgreSQL behavior or complies with ANSI specifications regarding the run order for user-defined trigger actions and triggers defined for internal constraints. Switching it off reverts back to PostgreSQL behavior, meaning triggers run in alphabetical order. As per the pg_settings catalog, this parameter is described as the following code: pgtraining=> select short_desc, extra_desc from pg_settings where name='ansi_constraint_trigger_ordering'; -[ RECORD 1 ]------------------------------------------------------------------------------------------------------------------ short_desc | Change the firing order of constraint triggers to be compatible with the ANSI SQL standard. extra_desc | When turned on, the firing order of constraint triggers in the after trigger queue is modified to be compatible with the ANSI SQL standard, while to the extent possible, while not changing the semantics of PostgreSQL applications that would have complied with the SQL standard without the parameter being turned on. Internal constraint triggers are fired first in alphabetical order, followed by user-defined constraint triggers in alphabetical order, followed by firing any other triggers, in alphabetical order. Let’s understand how this parameter affects your query behavior. PostgreSQL behavior In PostgreSQL, if two triggers have the same firing criteria (such as AFTER INSERT FOR EVERY ROW or BEFORE DELETE FOR EVERY ROW), the run order is decided based on their alphabetical order (pure ASCII sorting). The triggers with a name in uppercase are fired first, and followed by the triggers in lowercase in alphabetical order. This can be useful if you want to control the order of your triggers. For example, I can define two before insert triggers on a table pgbench_branches: pgbench_branches_trig_B_I_R_001 and pgbench_branches_trig_B_I_R_010. In this case, the trigger pgbench_branches_trig_B_I_R_001 fires before pgbench_branches_trig_B_I_R_010. ANSI standards SQL ANSI standards require that triggers be fired in the order in which they’re created. Although this makes sense, it adds an additional responsibility on programmers to drop and create all the triggers whenever introducing a new trigger. To make things easier, some of the engines implement an additional feature so you can specify an additional property—ORDER—while defining the trigger. PostgreSQL takes a different approach; it’s not hard to emulate what other engines offer with additional syntax by following a naming convention as we discussed. Internal triggers PostgreSQL implements internal and user-defined constraints as triggers. For example, even though we don’t define any trigger on pgbench_tellers, internal triggers are defined because of a referential integrity constraint (commonly referred to as a foreign key). Let’s look at the triggers currently defined on pgbench_tellers , which has four internal triggers. The internal triggers are defined to trigger an action or check whenever we use data modification language (DML) on pgbench_tellers: pgtraining=> select tgrelid::regclass trigger_table, tgname trigger_name, tgfoid::regproc trigger_function, tgisinternal is_trigger_internal, tgconstrrelid::regclass parent_table, tgconstraint::regclass, tginitdeferred is_constraint_trigger_initially_deferred, tgdeferrable is_constraint_trigger_deferrable from pg_trigger where tgrelid::regclass::text='pgbench_tellers'; trigger_table | trigger_name | trigger_function | is_trigger_internal | parent_table | tgconstraint | is_constraint_trigger_initially_deferred | is_cons traint_trigger_deferrable -----------------+------------------------------+------------------------+---------------------+------------------+--------------+------------------------------------------+-------- -------------------------- pgbench_tellers | RI_ConstraintTrigger_c_22663 | "RI_FKey_check_ins" | t | pgbench_branches | 22660 | f | f pgbench_tellers | RI_ConstraintTrigger_c_22664 | "RI_FKey_check_upd" | t | pgbench_branches | 22660 | f | f pgbench_tellers | RI_ConstraintTrigger_a_22676 | "RI_FKey_noaction_del" | t | pgbench_history | 22675 | f | f pgbench_tellers | RI_ConstraintTrigger_a_22677 | "RI_FKey_noaction_upd" | t | pgbench_history | 22675 | f | f (4 rows) Now let’s look at triggers defined on pgbench_branches. Triggers are defined to cascade or restrict an action to the child table when a DML fires on pgbench_branches. A set of triggers is defined for each parent or child table—pgbench_tellers and pgbench_accounts: pgtraining=> select tgrelid::regclass trigger_table, tgname trigger_name, tgfoid::regproc trigger_function, tgisinternal is_trigger_internal, tgconstrrelid::regclass parent_table, tgconstraint::regclass, tginitdeferred is_constraint_trigger_initially_deferred, tgdeferrable is_constraint_trigger_deferrable from pg_trigger where tgrelid::regclass::text='pgbench_branches'; trigger_table | trigger_name | trigger_function | is_trigger_internal | parent_table | tgconstraint | is_constraint_trigger_initially_deferred | is_con straint_trigger_deferrable ------------------+------------------------------+------------------------+ pgbench_branches | RI_ConstraintTrigger_a_22661 | "RI_FKey_noaction_del" | t | pgbench_tellers | 22660 | f | f pgbench_branches | RI_ConstraintTrigger_a_22662 | "RI_FKey_noaction_upd" | t | pgbench_tellers | 22660 | f | f pgbench_branches | RI_ConstraintTrigger_a_22666 | "RI_FKey_noaction_del" | t | pgbench_accounts | 22665 | f | f pgbench_branches | RI_ConstraintTrigger_a_22667 | "RI_FKey_noaction_upd" | t | pgbench_accounts | 22665 | f | f pgbench_branches | RI_ConstraintTrigger_a_22671 | "RI_FKey_noaction_del" | t | pgbench_history | 22670 | f | f pgbench_branches | RI_ConstraintTrigger_a_22672 | "RI_FKey_noaction_upd" | t | pgbench_history | 22670 | f | f (6 rows) Let’s add a new AFTER TRIGGER on pgbench_teller, which adds a row to pgbench_branches by selecting a row from pgbench_teller. We’re not using the new variable here to insert an incoming row. Instead, we’re getting a row that exists in pgbench_teller but the corresponding branch doesn’t exist in pgbench_branches: create or replace function fix_pgbench_branches() returns trigger as $body$ begin insert into public.pgbench_branches (bid,bbalance,filler) select t.bid, 0, 'the presence of this row in pgbench_tellers (child table) violates the SQL standard' from public.pgbench_tellers t where t.bid not in (select t1.bid from public.pgbench_branches t1); return NULL; end; $body$ language plpgsql; create trigger "teller_trig" after insert on public.pgbench_tellers for each row execute procedure fix_pgbench_branches(); Let’s look at the triggers currently defined on pgbench_tellers. In addition to the four internal triggers we saw earlier, the code contains a user-defined trigger (the one we just created): pgtraining=> select tgrelid::regclass trigger_table, tgname trigger_name, tgfoid::regproc trigger_function, tgisinternal is_trigger_internal, tgconstrrelid::regclass parent_table, tgconstraint::regclass, tginitdeferred is_constraint_trigger_initially_deferred, tgdeferrable is_constraint_trigger_deferrable from pg_trigger where tgrelid::regclass::text='pgbench_tellers'; trigger_table | trigger_name | trigger_function | is_trigger_internal | parent_table | tgconstraint | is_constraint_trigger_initially_deferred | is_cons traint_trigger_deferrable -----------------+------------------------------+------------------------+---------------------+------------------+--------------+------------------------------------------+-------- -------------------------- pgbench_tellers | RI_ConstraintTrigger_c_22663 | "RI_FKey_check_ins" | t | pgbench_branches | 22660 | f | f pgbench_tellers | RI_ConstraintTrigger_c_22664 | "RI_FKey_check_upd" | t | pgbench_branches | 22660 | f | f pgbench_tellers | RI_ConstraintTrigger_a_22676 | "RI_FKey_noaction_del" | t | pgbench_history | 22675 | f | f pgbench_tellers | RI_ConstraintTrigger_a_22677 | "RI_FKey_noaction_upd" | t | pgbench_history | 22675 | f | f pgbench_tellers | teller_trig | fix_pgbench_branches | f | - | - | f | f (5 rows) Let’s insert a row in pgbench_tellers where the bid does not yet exist in pgbench_branches: insert into public.pgbench_tellers (tid, bid, tbalance) values ( ( select max(tid)+1 from public.pgbench_tellers ), ( select max(bid)+1 from public.pgbench_branches ), 0 ); The insert fails with a foreign key violation constraint exception because before the user-defined trigger could fire and insert a row in pgbench_branches, the trigger related to the referential integrity constraint (RI_ConstraintTrigger_c_22663) was fired, which rejected the row: pgtraining=> insert into public.pgbench_tellers (tid, bid, tbalance) pgtraining-> values ( pgtraining(> ( select max(tid)+1 from public.pgbench_tellers ), pgtraining(> ( select max(bid)+1 from public.pgbench_branches ), pgtraining(> 0 pgtraining(> ); ERROR: insert or update on table "pgbench_tellers" violates foreign key constraint "pgbench_tellers_bid_fkey" DETAIL: Key (bid)=(50001) is not present in table "pgbench_branches". When multiple triggers meet the same firing criteria, they are fired in alphabetical order. For more information, see Overview of Trigger Behavior. If we have a different name for our trigger, it has a different impact: pgtraining=> alter trigger teller_trig ON public.pgbench_tellers RENAME TO "PGBENCH_TELLER_TRIGGER"; ALTER TRIGGER Now let’s execute our insert statement again: pgtraining=> insert into public.pgbench_tellers (tid, bid, tbalance) values ( ( select max(tid)+1 from public.pgbench_tellers ), ( select max(bid)+1 from public.pgbench_branches ), 0 ); INSERT 0 1 What changed in this case was the name of the trigger. Now that the trigger name is in uppercase and starts with P, it can fire before the trigger defined for the referential integrity constraint (RI_ConstraintTrigger_c_22663). This behavior of PostgreSQL isn’t compliant with ANSI specifications and it can cause incompatibility when migrating an application from another relational database. Effect of the Aurora PostgreSQL parameter Now let’s change the parameter ansi_constraint_trigger_ordering in the DB cluster parameter group with the Aurora instance we’re using for these tests: pgtraining=> show ansi_force_foreign_key_checks; ansi_force_foreign_key_checks ------------------------------- on (1 row) pgtraining=> show ansi_constraint_trigger_ordering ; ansi_constraint_trigger_ordering ---------------------------------- on (1 row) pgtraining=> insert into public.pgbench_tellers (tid, bid, tbalance) values ( ( select max(tid)+1 from public.pgbench_tellers ), ( select max(bid)+1 from public.pgbench_branches ), 0 ); ERROR: insert or update on table "pgbench_tellers" violates foreign key constraint "pgbench_tellers_bid_fkey" DETAIL: Key (bid)=(50002) is not present in table "pgbench_branches". This parameter makes sure that PostgreSQL follows the ANSI specifications. It ensures that internal constraint triggers are fired first, followed by user-defined constraint triggers, then user-defined triggers. If you’re using an application that’s compatible with PostgreSQL and prefer to stick to default behavior, you can switch this off in the DB cluster parameter group. Although you can’t change this parameter for a specific transaction or session, a change to this parameter is dynamic and doesn’t require a restart of the DB instance. ansi_force_foreign_key_checks This parameter controls whether Aurora PostgreSQL retains PostgreSQL behavior or complies with ANSI specifications for imposing foreign key constraints when a cascaded action is defined in the constraint. Switching it off reverts back to PostgreSQL behavior. The following description is provided in pg_settings: pgtraining=> select name, short_desc, extra_desc from pg_settings where name like 'ansi_force_foreign_key_checks'; -[ RECORD 1 ]----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- name | ansi_force_foreign_key_checks short_desc | Ensure referential actions such as cascaded delete or cascaded update will always occur regardless of the various trigger contexs that exist for the action. extra_desc | When turned on, Ensure referential actions such as cascaded delete or cascaded update will always occur regardless of the various trigger contexs that exist for the action. Let’s understand how this parameter affects your query behavior. ANSI standards SQL ANSI standards require that any operation cascaded to a child table because of a referential integrity constraint should be applied irrespective of trigger actions defined on the child table. Let’s consider an example of a trigger that is defined on a child table to trigger upon delete and the trigger is defined to skip deletion and perform some other operation instead. Now if we delete a row from the parent table, it will lead to delete on the child table as well. In such a scenario, the trigger will not impact cascaded delete operation and the rows from the child table will be removed irrespective of the trigger behavior defined. PostgreSQL behavior For PostgreSQL, because the referential integrity constraints are defined as an AFTER trigger, there is a chance that a cascaded delete or cascaded update for a child table is skipped as an effect of a BEFORE trigger that exists on the child table. This leaves the database in an inconsistent state which is hard to debug unless you drop and recreate the foreign key constraint. The inconsistency also makes it hard to trust table metadata information (foreign key constraint) for the purpose of query optimization, such as removing redundant inner joins on the guarantees of referential integrity constraints. Let’s see how it works in a practical scenario. In the following code, we make changes to the foreign key constraint on pgbench_teller and pgbench_accounts so that any DELETE on the parent table (pgbench_branches) is also CASCADED to these child tables: pgtraining=> alter table pgbench_tellers drop constraint pgbench_tellers_bid_fkey; ALTER TABLE pgtraining=> alter table pgbench_tellers add constraint pgbench_tellers_bid_fkey FOREIGN KEY (bid) REFERENCES pgbench_branches(bid) on delete cascade; ALTER TABLE pgtraining=> alter table pgbench_accounts drop constraint pgbench_accounts_bid_fkey ; ALTER TABLE pgtraining=> alter table pgbench_accounts add constraint pgbench_accounts_bid_fkey FOREIGN KEY (bid) REFERENCES pgbench_branches(bid) on delete cascade; ALTER TABLE Now suppose we have a requirement to ensure that tellers are not removed from pgbench_teller if they still hold some balance (if the tbalance is more than 0). Let’s add a trigger on pgbench_teller to reject such deletes: CREATE OR REPLACE FUNCTION public.deny_delete_pgbench_teller() RETURNS trigger LANGUAGE plpgsql AS $function$ begin IF old.tbalance > 0 THEN RETURN NULL; END IF; RETURN OLD; end; $function$ CREATE TRIGGER deny_delete_of_non_zero_teller BEFORE DELETE ON pgbench_tellers FOR EACH ROW EXECUTE PROCEDURE deny_delete_pgbench_teller() ; To test if the trigger is working or not, we can delete a branch which has more than a 0 balance. In my dataset generated by pgbench, row with tid=1 in pgbench_tellers is one such row: pgtraining=> select count(*) from pgbench_tellers where tid=1; count ------- 1 (1 row) pgtraining=> pgtraining=> delete from pgbench_tellers where bid=1; DELETE 0 pgtraining=> select count(*) from pgbench_tellers where tid=1; count ------- 1 (1 row) Now let’s delete a row from the parent table – pgbench_branches: pgtraining=> delete from pgbench_branches where bid=1; After this delete, the database is left in an inconsistent state: pgtraining=> select count(*) from pgbench_branches where bid=1; count ------- 0 (1 row) pgtraining=> select count(*) from pgbench_tellers where bid=1; count ------- 10 (1 row) Not only does this violate the behavior for the foreign key defined by ANSI, it also makes it hard for the database optimizer to perform optimizations like removing redundant joins. For example, the optimization that we discussed in the previous part of this blog series (part 3), with pgbench_v_teller view, can’t be applied. Skipping a join with pgbench_branches would now produces inconsistent results: pgtraining=> set apg_enable_remove_redundant_inner_joins =on; SET pgtraining=> explain analyze select tid,bid,tbalance from pgbench_v_teller; QUERY PLAN ------------------------------------------------------------------------------------------------------------------------------------------ Hash Join (cost=1673.10..12055.73 rows=500002 width=12) (actual time=11.885..147.258 rows=499992 loops=1) Hash Cond: (teller.bid = branches.bid) -> Seq Scan on pgbench_tellers teller (cost=0.00..9070.02 rows=500002 width=12) (actual time=0.004..33.633 rows=500002 loops=1) -> Hash (cost=1013.60..1013.60 rows=52760 width=4) (actual time=11.639..11.639 rows=50001 loops=1) Buckets: 65536 Batches: 1 Memory Usage: 2270kB -> Seq Scan on pgbench_branches branches (cost=0.00..1013.60 rows=52760 width=4) (actual time=0.005..5.507 rows=50001 loops=1) Planning Time: 0.146 ms Execution Time: 165.517 ms (8 rows) If we drop and try to recreate the foreign key constraint, it fails: pgtraining=> alter table pgbench_tellers drop constraint pgbench_tellers_bid_fkey ; ALTER TABLE pgtraining=> alter table pgbench_tellers add constraint pgbench_tellers_bid_fkey FOREIGN KEY (bid) REFERENCES pgbench_branches(bid) on delete cascade; ERROR: insert or update on table "pgbench_tellers" violates foreign key constraint "pgbench_tellers_bid_fkey" DETAIL: Key (bid)=(1) is not present in table "pgbench_branches". Let’s fix the data and add a foreign key: pgtraining=> insert into pgbench_branches values (1,(select sum(tbalance) from pgbench_tellers where bid=1), ' '); INSERT 0 1 pgtraining=> alter table pgbench_tellers add constraint pgbench_tellers_bid_fkey FOREIGN KEY (bid) REFERENCES pgbench_branches(bid) on delete cascade; ALTER TABLE Effect of the Aurora PostgreSQL parameter Now use the Amazon Relational Database Service (Amazon RDS) console to change the parameter ansi_force_foreign_key_checks in the DB cluster parameter group. Let’s run the delete statement again: pgtraining=> show ansi_force_foreign_key_checks ; ansi_force_foreign_key_checks ------------------------------- on (1 row) pgtraining=> delete from pgbench_branches where bid=1; ERROR: Attempt to suppress referential action with before trigger. CONTEXT: SQL statement "DELETE FROM ONLY "public"."pgbench_tellers" WHERE $1 OPERATOR(pg_catalog.=) "bid"" pgtraining=> pgtraining=> pgtraining=> pgtraining=> pgtraining=> select count(*) from pgbench_branches where bid=1; count ------- 1 (1 row) pgtraining=> select count(*) from pgbench_tellers where bid=1; count ------- 10 (1 row) When ansi_force_foreign_key_checks is enabled, Aurora PostgreSQL makes sure that the referential integrity constraint is enforced irrespective of trigger context for user-defined triggers. If the triggers attempt to suppress or skip the cascaded DELETE or cascaded UPDATE, the original action on the parent table is also rolled back. If you’re using an application that’s compatible with PostgreSQL and prefer to stick to the default behavior, you can switch this off in the DB cluster parameter group. Although you can’t change this parameter for a specific transaction or session, a change to this parameter is dynamic and doesn’t require a restart of the DB instance. ansi_qualified_update_set_target This parameter controls if Aurora PostgreSQL retains PostgreSQL’s default behavior when parsing the column name in the SET clause of an UPDATE statement, or if it accepts syntax that’s consistent with what’s allowed by Oracle and SQL Server. The following is the description in the pg_settings view: pgtraining=> select name, short_desc, extra_desc from pg_settings where name like 'ansi_qualified_update_set_target'; -[ RECORD 1 ]------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ name | ansi_qualified_update_set_target short_desc | Support table and schema qualifiers in UPDATE ... SET statements. e.g. UPDATE t SET s.t.c = v WHERE p.off provides community PostgreSQL semantics and on provides this feature. extra_desc | When turned on, the UPDATE ... SET syntax is consistent with what's allowed by Oracle and SQL/Server, and can reduce migration effort. PostgreSQL allows composite types subfields to be set using syntax that is potentially ambiguous with respect to the syntax that Oracle and SQL/Server accept. In cases where the syntax is ambiguous, an ERROR message will be raised to inform the user that the SET target is ambiguous. PostgreSQL behavior The following code is the UPDATE syntax as per PostgreSQL documentation: [ WITH [ RECURSIVE ] with_query [, ...] ] UPDATE [ ONLY ] table_name [ * ] [ [ AS ] alias ] SET { column_name = { expression | DEFAULT } | ( column_name [, ...] ) = [ ROW ] ( { expression | DEFAULT } [, ...] ) | ( column_name [, ...] ) = ( sub-SELECT ) } [, ...] [ FROM from_item [, ...] ] [ WHERE condition | WHERE CURRENT OF cursor_name ] [ RETURNING * | output_expression [ [ AS ] output_name ] [, ...] ] The column_name can be specified in the table named by table_name. The column name can be qualified with a subfield name or array subscript, if needed. Don’t include the table’s name in the specification of a target column. For example, UPDATE table_name SET table_name.col = 1 is invalid. PostgreSQL throws an exception if UPDATE queries have a fully qualified table name or even a column name with a table name prefix in the SET clause: pgtraining=> update public.pgbench_tellers set pgbench_tellers.tbalance=1000 where tid=1; ERROR: column "pgbench_tellers" of relation "pgbench_tellers" does not exist LINE 1: update public.pgbench_tellers set pgbench_tellers.tbalance=1... ^ pgtraining=> pgtraining=> update public.pgbench_tellers set public.pgbench_tellers.tbalance=1000 where tid=1; ERROR: column "public" of relation "pgbench_tellers" does not exist LINE 1: update public.pgbench_tellers set public.pgbench_tellers.tba... As the exception explains, PostgreSQL is expecting pgbench_terllers or public to be a column and tbalance to be a subfield. This behavior of PostgreSQL can increase the effort required to port application code when migrating from commercial engines like Oracle and SQL Server. Effect of the Aurora PostgreSQL parameter The commercial engines allow both syntaxes and we can set Aurora PostgreSQL to behave the same way by setting ansi_qualified_update_set_target to on: pgtraining=> set ansi_qualified_update_set_target=on; SET pgtraining=> pgtraining=> update public.pgbench_tellers set public.pgbench_tellers.tbalance=1000 where tid=1; UPDATE 1 pgtraining=> update public.pgbench_tellers set pgbench_tellers.tbalance=1000 where tid=1; UPDATE 1 This can be useful when migrating an application from Oracle or SQL Server. It allows UPDATE statements in your application with Oracle or SQL Server-compatible syntax to work with Aurora PostgreSQL with little or no change. You can set this parameter in the DB cluster parameter group or at the session level. A change to this parameter doesn’t require a restart of the DB instance. Conclusion Aurora PostgreSQL has several levers by way of parameters that allow for ANSI compliance, which helps a great deal if you’re migrating from other engines to Aurora PostgreSQL. As part of this four part blog series, we covered parameters related to memory and query plan management in part one. In part two, we covered replication, security and logging parameters. Part three and part four, covered detailed explanation of parameters that can be used to modify Aurora PostgreSQL behavior to improve query performance and increase adherence to ANSI standard, which is helpful while migrating applications from other database engines. AWS continues to iterate on customer feedback and improve Aurora, which offers enterprise-grade features on popular open-source database engines. About the authors Sameer Kumar is a Database Specialist Technical Account Manager at Amazon Web Services. He focuses on Amazon RDS, Amazon Aurora and Amazon DocumentDB. He works with enterprise customers providing technical assistance on database operational performance and sharing database best practices.       Gopalakrishnan Subramanian is a Database Specialist solutions architect at Amazon Web Services. He works with our customers to provide guidance and technical assistance on database projects, helping them improving the value of their solutions when using AWS https://aws.amazon.com/blogs/database/amazon-aurora-postgresql-parameters-part-4-ansi-compatibility-options/

[seocaonweb-blog]

IMPORT EXPORT CODE REGISTRATION

Import Export Code Registration: A Key Step for Your Business Expansion

In today’s globalized world, expanding your business beyond borders is a profitable opportunity. However, to engage in international trade legally, you need an Import Export Code (IEC). Caonweb will guide you through the process of IEC code registration, highlighting the significance of this vital document for your business growth.

In this article, we will delve into the significance of IEC code registration, its benefits, and how to obtain it conveniently.

Table of Contents

About Import Export Code (IEC)

Where is IEC applicable?

Where Import-Export Code Registration. is not applicable.

Documents required for IEC (Import Export Code) Registration.

Steps in the process of IEC (Import/Export Code) Registration.

Benefits of taking IEC (Import Export Code) Registration

Expert Insights

FAQs

Conclusion

Conditions where IEC is applicable?

1-At the time of customs clearance of goods by Importer IEC is required by customs authorities.

2- At the time of sending his goods by exporter IEC is required by the customs port.

3- At the time of sending money abroad through banks IEC is required by the bank.

4- At the time of receiving money in foreign currency directly into his bank account then IEC is required by the bank.

Conditions where IEC is not applicable?

IEC is not mandatory for all GST-Registered traders. PAN can be used as a new IEC code for import/export purposes. No IEC is required for personal use, government departments, ministries, and notified charitable institutions.

Steps involved in IEC (Import/Export Code) Registration

To register IEC, visit the DGFT website.

Go to the ‘Services’ tab on the homepage.

Select the ‘IEC Profile Management’ from the drop-down list.

Select the ‘Apply for IEC’ option.

Click on the ‘Register’ option. Fill in the required details and click the ‘Sent OTP’ button.

Insert OTP and register by clicking the ‘Register’ button.

After validating the OTP successfully, you will receive a temporary password, which can be further changed after logging into the DGFT website.

After registering on the DGFT website, login to the website by entering the username and password.

Go to the ‘Apply for IEC’ option on the DGFT website.

Click on the ‘Start Fresh Application’ button.

Enter the general information, details of proprietor/partner/director/Karta/managing trustee, bank information, and other details, attach a Digital Signature Certificate (DSC) and make the payment.

After successful payment, it will be redirected to the DGFT website. The receipt will be displayed. Download the receipt for future reference.

The IEC Certificate is sent via email. It can be downloaded after logging in to the DGFT website and clicking the ‘Print IEC’ option under the ‘IEC Profile Management’.

List of documents required for IEC (Import Export Code) Registration

Individuals, firms, or company’s copy of PAN Card.

Provide a copy of the proprietor’s Aadhaar card, voter ID, or passport.

Proof of establishment, incorporation or registration of the partnership, society, proprietorship firm, Pvt. company, HUF, etc. 

Proof of address of business premises, such as sale deed, lease deed, rent agreement or utility bills (electricity bill, telephone bill or mobile bill).

Enclose copies of current bank account cancellation cheques for individuals, companies or firms.

Also provide a self-addressed envelope for delivery of the IEC certificate by registered post.

Benefits of IEC registration

1-Expansion of business

IEC helps businesses expand globally and grow with their services/products.

2-Availing several benefits

The IEC registration enables companies to avail benefits for their imports/exports from DGFT, Export Promotion Council, Customs, etc.

3-No return filing

IEC registration does not require any return filings of export / Import transactions, there is no requirement to file returns with DGFT.

4-Easy processing

Obtaining an IEC code from the DGFT is a straightforward process that doesn’t require any proof of export or import. The application can be submitted and the IEC code can be obtained within 10 to 15 days.

Expert Insights: CA Sakshi Agarwal

When it comes to the intricacies of IEC code registration and its implications for your business, CA Sakshi Agarwal, a seasoned professional in international taxation and cross-border business, shares her insights and expertise to help you navigate the registration process effortlessly.

Why Caonweb is Your Trusted Business Name

For a seamless IEC code registration experience, Noida-based Tax consultants “Caonweb” stands out as a reliable and trustworthy name in the industry. Under the guidance of our expert team and a client-centric approach, we ensure the registration process is not only efficient but also compliant with all legal norms.

Frequently Asked Questions

Q1. What is the IEC code?

The IEC code, or Import-Export Code, is a 10-digit identification number required for businesses engaged in international trade.

Q2. How can I apply for an IEC code online?

You can apply for an IEC code online through the DGFT’s website by providing the necessary documents and details.

Q3. What are the benefits of having an IEC code?

Having an IEC code allows your business to engage in international trade, ensures legal compliance, and provides access to government incentives.

Q4. How long does it take to obtain an IEC code?

Typically, an IEC code is issued within 1-2 working days of applying online.

Q5. Why choose Caonweb for IEC code registration?

Caonweb is a trusted business name known for its expert guidance and client-centric approach, ensuring a smooth and compliant registration process.

Conclusion

In conclusion, the Import Export Code (IEC) is a crucial requirement for businesses looking to engage in international trade. Its benefits are numerous, and with the convenience of online registration and expert guidance from CA Sakshi Agarwal, obtaining your IEC code has never been easier. Choose Caonweb for a seamless experience and take the first step towards expanding your business globally.

In this article, we’ve covered the essentials of IEC code registration, from its significance to the online application process and the benefits it offers. With expert insights from CA Sakshi Agarwal and the trusted assistance of Caonweb, you can confidently pursue your international business ventures. Don’t miss out on the opportunities that global trade has to offer. Get your IEC code today and unlock a world of possibilities.

Source: IMPORT EXPORT CODE REGISTRATION

[targetenterprises-blog]

Looking for Import Export Consultants? Target Enterprises provides various import-export registration services such as EPCG Licence, Advance Licence, NSIC Registration, DGFT Consultants, IEC Code, IEC Code Online, Import-Export Code, IEC Modification, Import-Export License Fees, IEC Application Form & many more with Easy, Reliable and 100% Secured Process.For more info, please visit at http://targetenterprises.in/