Using Visual Studio Code Extension for Development

The Oracle NoSQL Database Cloud Service provides an extension for Microsoft Visual Studio Code which lets you connect to a running instance of Oracle NoSQL Database Cloud Service.

You can use Oracle NoSQL Database Visual Studio (VS) Code extension to:

This article has the following topics:

Installing Oracle NoSQL Database Visual Studio Code Extension

You can install the Oracle NoSQL Database VS Code extension from the Visual Studio Marketplace for online installation.

Before you can install the Oracle NoSQL Database Visual Studio (VS) Code extension, you must install Visual Studio Code. You can download Visual Studio Code from here.

For installation:

  1. In Visual Studio Code, click the Extensions icon in the left navigation.

    Visual Studio Code Activity Bar

    Alternatively, you can open the Extensions view by pressing:

    • (Windows and Linux) Control + Shift + X

    • (macOS) Command + Shift + X.

  2. Search Oracle NoSQL Database Connector in the extension marketplace.

  3. Click Install on the Oracle NoSQL Database Connector extension

Connecting to Oracle NoSQL Database Cloud Service or Oracle NoSQL Database Cloud Simulator from Visual Studio Code

Oracle NoSQL Database Visual Studio (VS) Code extension provides two methods to connect to Oracle NoSQL Database Cloud Service or Oracle NoSQL Database Cloud Simulator.

You can either provide a config file with the connection information or fill in the connection information in the specific fields. If you are using a driver, for example, a Node.js driver and already have connection details saved in a file or want to create one, use the Use Configuration File option to connect to the Oracle NoSQL Database Cloud Service. Otherwise, if you are creating a new connection, use the Advanced option.

  1. In Visual Studio Code, click the Oracle NoSQL DB view in the Activity Bar.

    Visual Studio Code Activity Bar

  2. Open the Oracle NoSQL DB Show Connection Settings page from the Command Palette or the Oracle NoSQL DB view in the Activity Bar.

    • Open from Command Palette

      1. Open the Command Palette by pressing:

        • (Windows and Linux) Control + Shift + P

        • (macOS) Command + Shift + P

      2. From the Command Palette, select OracleNoSQL: Show Connections Settings.

        Tip:

        Enter oraclenosql in the Command Palette to display all of the Oracle NoSQL DB commands you can use.

- Open from Oracle NoSQL DB View
  1. Expand the **TABLE EXPLORER** pane in the left navigation if it's collapsed.

  2. Click **Add Connection** to open the Oracle NoSQL DB **Show Connection Settings** page.

  1. In the Show Connection Settings page, click Cloud or CloudSim to connect to Oracle NoSQL Database Cloud Service or Oracle NoSQL Database Cloud Simulator.

  2. Click Add New Connection and enter the connection information. Click Add.

    Table - Cloud Connection Parameters

    Field Description Sample Value
    Connection Name: A unique name, for the connection specification is mandatory from the plugin version 4.0.0. Updating the Connection Name field is recommended after upgrading the plugin from version 3.0.0 or lower.

    Note: You can add multiple connections and the stored connection specifications are persistent.    		  
    Region/Endpoint: A Region Identifier or Service Endpoint to access the Oracle NoSQL Database Cloud Service. See, Data Regions and Associated Service URLs for a list of Region Identifiers and Service Endpoints. us-ashburn-1 or https://nosql.us-ashburn-1.oci.oraclecloud.com (for the Ashburn Oracle NoSQL Database Cloud Service region identifier in the North America region).
    Tenant OCID: Tenancy’s OCID for your Oracle NoSQL Database Cloud Service. See Where to Get the Tenancy’s OCID and User’s OCID in Oracle Cloud Infrastructure Documentation. ocid1.tenancy.oc1..<unique_ID>
    User OCID: User’s OCID for your Oracle NoSQL Database Cloud Service. See Where to Get the Tenancy’s OCID and User’s OCID in Oracle Cloud Infrastructure Documentation. ocid1.user.oc1..<unique_ID>
    Fingerprint: Fingerprint for the private key that was added to this user.<p>The fingerprint of the signing key is created while generating and uploading the API Signing Key. See How to Get the Key’s Fingerprint in Oracle Cloud Infrastructure Documentation. 12:34:56:78:90:ab:cd:ef:12:34:56:78:90:ab:cd:ef
    Private Key File: Browse to the location where private key is stored. See How to Generate an API Signing Key to generate the signing key with an optional pass phrase. /home/user/.oci/oci_api_key.pem
    Passphrase: Passphrase you specified when creating the private key. The pass phrase of the signing key is created while generating and uploading the API Signing Key. See How to Get the Key’s Fingerprint in Oracle Cloud Infrastructure Documentation.
    Required, only if the key is encrypted.    		  
    Compartment: The name or OCID of the compartment for your Oracle NoSQL Database Cloud Service schema.

    If you do not provide any value, the field defaults to the root compartment.

    You create compartments in Oracle Cloud Infrastructure Identity and Access Management (IAM). See Setting Up Your Tenancy and Managing Compartments in Oracle Cloud Infrastructure Documentation .

    		- Compartment name: mycompartment

    - Compartment name qualified with its parent compartment: parent.childcompartment

    - Compartment OCID: ocid1.tenancy.oc1...<unique_ID>

    Table - CloudSim Connection Parameters

    Field Description Sample Value
    Connection Name: A unique name, for the connection specification is mandatory from the plugin version 4.0.0. Updating the Connection Name field is recommended after upgrading the plugin from version 3.0.0 or lower.

    Note: You can add multiple connections and the stored connection specifications are persistent.    		  
    Endpoint: Service Endpoint URL of the Oracle NoSQL Database Cloud Simulator instance. http://myinstance.cloudsim.com:8080

    If you do not specify the value, it defaults to http://localhost:8080.
    Tenant Identifier: Unique identifier to identify the tenant. Tenant01

    If you do not specify the value, it defaults to TestTenant.

    Note: The connection processing has changed starting with version 4.0.0. If you are using an older version of the plugin, then only the most recently used connection will be migrated during the upgrade process to version 4.0.0. The plugin will automatically assign the name cloud_old0 to the migrated connection. You can change the connection name using the Modify Connection option in the Connections Setting page.

  3. The connection details are saved. To modify existing connections, select the connection from the Connections drop-down. Click Modify Connection. Make the desired changes in the Connection Parameters and click Save.

  4. Click the Web Icon in the TABLE EXPLORER to view the list of all the connections (on-premises and Cloud) present in the plugin. The connections are displayed in the dropdown in the format: Connection Name:Endpoint: Compartment (if specified).

    Choose the connection from the list and select Connect. The Visual Studio Code plugin connects to Oracle NoSQL Database Cloud Serviceor Oracle NoSQL Database Cloud Simulator and displays all its tables in the Table Explorer window.

  1. If you don’t have a config file, create one, for example, config.json or a file with the JSON object. The config file format for connecting to Oracle NoSQL Database Cloud Service or Oracle NoSQL Database Cloud Simulator is as shown below.

    Table - Configuration Templates

    Oracle NoSQL Database Cloud Service Oracle NoSQL Database Cloud Simulator
    Configuration template to connect using OCI configuration file
    { "region": "", "compartment": "", "auth": { "iam": { "configFile": "",  "profileName": "" } } }
    Configuration template to connect using IAM authentication credentials
    { "region": "", "compartment": "", "auth": { "iam": { "tenantId": "", "userId": "", "fingerprint": "", "privateKeyFile": "", "passphrase": "" } } }
    		 
    { "endpoint": "http://myinstance.cloudsim.com:8080", "auth" : "Bearer" }

  2. Open the Oracle NoSQL DB Show Connection Settings page from the Command Palette or the Oracle NoSQL DB view in the Activity Bar.

    • Open from Oracle NoSQL DB View

      • Expand the Table Explorer pane in the left navigation if it’s collapsed.

      • Click Add Connection to open the Oracle NoSQL DB Show Connection Settings page.

      • In the Show Connection Settings page, click Cloud to connect to Oracle NoSQL Database.

      • Enter the connection information and click Add.

        Table - Cloud Connection Parameters

        Field Description Sample Vaue
        Connection Name: A unique name, for the connection specification is mandatory from the plugin version 4.0.0. Updating the Connection Name field is recommended after upgrading the plugin from version 3.0.0 or lower.

        Note: You can add multiple connections and the stored connection specifications are persistent.        		  
        Region/Endpoint: A Region Identifier or Service Endpoint to access the Oracle NoSQL Database Cloud Service. See, Data Regions and Associated Service URLs for a list of Region Identifiers and Service Endpoints. us-ashburn-1 or https://nosql.us-ashburn-1.oci.oraclecloud.com (for the Ashburn Oracle NoSQL Database Cloud Service region identifier in the North America region).
        Configuration File: Browse to the location where the OCI configuration file is stored. /home/user/security/config/oci.config
        Profile: Name of the configuration profile to be used to connect to the Oracle NoSQL Database Cloud Service. If you do not specify this value, the field defaults to the DEFAULT profile ADMIN_USER
        Compartment: The name or OCID of the compartment for your Oracle NoSQL Database Cloud Service schema.

        If you do not provide any value, the field defaults to the root compartment.

        You create compartments in Oracle Cloud Infrastructure Identity and Access Management (IAM). See Setting Up Your Tenancy and Managing Compartments in Oracle Cloud Infrastructure Documentation.

        • Compartment name

          mycompartment

        • Compartment name qualified with its parent compartment

          parent.childcompartment

        • Compartment OCID

          ocid1.tenancy.oc1...

Note: The connection processing has changed starting with version 4.0.0. If you are using an older version of the plugin, then only the most recently used connection will be migrated during the upgrade process to version 4.0.0. The plugin will automatically assign the name cloud_old0 to the migrated connection. You can change the connection name using the Modify Connection option in the Connections Setting page.

  • Open from Command Palette:

    • Open the Command Palette by pressing:

      • (Windows and Linux) Control + Shift + P

      • (macOS) Command + Shift + P

    • From the Command Palette, select Oracle NoSQL: Connect via Config File.

      Note: Enter oraclenosql in the Command Palette to display all of the Oracle NoSQL DB commands you can use.

    • Browse to the location where the *.config file is stored and click Select.

  1. The connection details are saved. To modify existing connections, select the connection from the Connections drop-down. Click Modify Connection. Make the desired changes in the Connection Parameters and click Save.

  2. Click the Web Icon in the TABLE EXPLORER to view the list of all the connections (on-premises and Cloud) present in the plugin. The connections are displayed in the dropdown in the format: Connection Name:Endpoint: Compartment (if specified).

    Choose the connection from the list and select Connect. The Visual Studio Code plugin connects to Oracle NoSQL Database Cloud Serviceor Oracle NoSQL Database Cloud Simulator and displays all its tables in the Table Explorer window.

Creating applications using Oracle NoSQL Java SDK from Visual Studio Code

Learn to create applications from Visual Studio Code extension using the Oracle NoSQL Java SDK package.

After connecting to the Oracle NoSQL Database Cloud Simulator or Oracle NoSQL Database Cloud Service, you can create applications using Oracle NoSQL Java SDK.

Perform the following steps:

Set up the Maven Project

  1. Open Visual Studio Code.

  2. Install the Java Extension Pack:

    1. Open the Extensions view by clicking the Extensions icon in the left sidebar.

    2. Search for Java Extension Pack in the Extensions Marketplace.

    3. Click the Install button to install the Java Extension Pack

  3. On the View tab, select Command Palette and press Ctrl+Shift+P.

  4. Search for Java: New Project.

  5. Choose the project template as Maven.

  6. Enter the project details:

    • Project name.

    • Project location (default is the current workspace folder).

    • Package name (For example, com.example.myproject).

  7. Set the Java path in your environment variable.

  8. Visual Studio Code creates the project directory structure and files.

  9. Open the pom.xml file from the project directory and add the Oracle NoSQL Java SDK dependency as follows. Use the latest version. See Oracle NoSQL Java SDK.

    <dependency>
<groupId>com.oracle.nosql</groupId>
<artifactId>nosqldb-driver</artifactId>
<version>5.4.22</version>
</dependency>

Create and run a sample application program

  1. Create a sample application code as follows. Update your region in <your_region_identifier> and compartment OCID in <ocid_of_your_compartment> placeholders.

    Note: This application retrieves authentication details from the OCI configuration file. For more information about the configuration file and its contents, see Authentication to connect to Oracle NoSQL Database.

    package org.oracle.nosqljavasdk;

import oracle.nosql.driver.NoSQLHandle;
import oracle.nosql.driver.NoSQLHandleConfig;
import oracle.nosql.driver.NoSQLHandleFactory;
import oracle.nosql.driver.iam.SignatureProvider;
import oracle.nosql.driver.ops.GetRequest;
import oracle.nosql.driver.ops.GetResult;
import oracle.nosql.driver.ops.PutRequest;
import oracle.nosql.driver.ops.PutResult;
import oracle.nosql.driver.ops.TableLimits;
import oracle.nosql.driver.ops.TableRequest;
import oracle.nosql.driver.ops.TableResult;
import oracle.nosql.driver.values.MapValue;

public class JavaVSCodeCloud {
    /* Name of your table */
    final static String tableName = "TestSDK";
    static NoSQLHandle handle;
    /* replace the placeholder with the name of your region for example Region.US_ASHBURN_1*/
    /* String region ="<your_region_identifier>";  */

    public static void main(String[] args) throws Exception {
      String region ="<your_region_identifier>";
      String compId ="<ocid_of_your_compartment>";
      handle = generateNoSQLHandleCloud(region,compId);
        try {
            createTable(handle);
            writeRows(handle);
            readRows(handle);
                          /* Uncomment this if you want to drop the table */
            //dropTable(handle);
        } catch (Exception e) {
            System.err.print(e);
        } finally {
            handle.close();
        }
    }

   /* Create a NoSQL handle to access the cloud service */
   private static NoSQLHandle generateNoSQLHandleCloud(String region, String compId) throws Exception {
      SignatureProvider ap = new SignatureProvider();
      NoSQLHandleConfig config = new NoSQLHandleConfig(region, ap);
      /* set your default compartment */
      config.setDefaultCompartment(compId);
      NoSQLHandle handle = NoSQLHandleFactory.createNoSQLHandle(config);
      return handle;
   }

    /**
     * Create a simple table with an integer key
     * and a single string data field
     * and set your desired table capacity
     */
    private static void createTable(NoSQLHandle handle) throws Exception {
        String createTableDDL = "CREATE TABLE IF NOT EXISTS " +
            tableName + "(employeeid INTEGER, name STRING, " +
            "PRIMARY KEY(employeeid))";

        TableLimits limits = new TableLimits(1, 2, 1);
        TableRequest treq = new TableRequest()
            .setStatement(createTableDDL).setTableLimits(limits);

        System.out.println("Creating table " + tableName);
        TableResult tres = handle.tableRequest(treq);

        /* The request is async,
         * so wait for the table to become active.
        */
        System.out.println("Waiting for "

            + tableName + " to become active");
        tres.waitForCompletion(handle, 60000, /* wait 60 sec */
            1000); /* delay ms for poll */
        System.out.println("Table " + tableName + " is active");
    }

    /**
     * Construct a row and add it to the table
     */
    private static void writeRows(NoSQLHandle handle) throws Exception {
        MapValue value =
            new MapValue().put("employeeid", 1).put("name", "Tracy");
        PutRequest putRequest =
            new PutRequest().setValue(value).setTableName(tableName);
        PutResult putResult = handle.put(putRequest);
        if (putResult.getVersion() != null) {
            System.out.println("Wrote " + value);
        } else {
            System.out.println("Put failed");
        }
    }

    /**
     * Set a key and read the row from the table
     */
    private static void readRows(NoSQLHandle handle) throws Exception {
        MapValue key = new MapValue().put("employeeid", 1);
        GetRequest getRequest =
            new GetRequest().setKey(key).setTableName(tableName);
        GetResult getRes = handle.get(getRequest);
        System.out.println("Read " + getRes.getValue());
    }

    /**
     * Drop the table and wait for the table to move to dropped state
     */
    private static void dropTable(NoSQLHandle handle) throws Exception {
        System.out.println("Dropping table " + tableName);
        TableRequest treq = new TableRequest()
            .setStatement("DROP TABLE IF EXISTS " + tableName);
        TableResult tres = handle.tableRequest(treq);
        System.out.println("Waiting for " + tableName + " to be dropped");
        tres.waitForCompletion(handle, 60000, /* wait 60 sec */
            1000); /* delay ms for poll */
        System.out.println("Table " + tableName + " has been dropped");
    }
}

  2. Run the Java program. You can press F5 or select the desired option from the Run menu.

    Note: If you have network proxies, include them in the settings.xml file located in the maven directory.

  3. You can view the output in the Visual Studio Code terminal.

The application code above creates the table TestSDK, adds a row to the table, and reads the row from the table.

Sample output:

----------------< com.oracle.nosql.example:NoSQLOperation >-----------------
Building NoSQLOperation 1.0-SNAPSHOT
  from pom.xml
--------------------------------[ jar ]---------------------------------

--- resources:3.3.1:resources (default-resources) @ NoSQLOperation ---
Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
skip non existing resourceDirectory C:\Users\ramya\javaVSCode\src\main\resources

--- compiler:3.8.0:compile (default-compile) @ HelloWorld ---
Changes detected - recompiling the module!
File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
Compiling 1 source file to C:\Users\ramya\javaVSCode\target\classes

--- exec:3.1.0:exec (default-cli) @ NoSQLOperation ---
Creating table TestSDK
Waiting for TestSDK to become active
Table TestSDK is active
Wrote {"name":"Tracy","employeeid":1}
Read {"employeeid":1,"name":"Tracy"}
------------------------------------------------------------------------
BUILD SUCCESS
------------------------------------------------------------------------
Total time:  8.013 s
Finished at: 2025-11-24T17:01:24+05:30
------------------------------------------------------------------------

You can also view the table from your Visual Studio Code Table Explorer. For details, see Managing Tables Using Visual Studio Code Extension.

Managing Tables Using Visual Studio Code Extension

After you connect to your deployment using Oracle NoSQL Database Visual Studio (VS) Code extension, use the TABLE EXPLORER located on the left navigation to:

You can also:

Explore tables, columns, indexes and keys

When you expand an active connection, Oracle NoSQL Database VS Code shows the tables in that deployment.

Perform DDL operations using Visual Studio Code

You can use Visual Studio Code to perform DDL operations.

Some of the DDL operations that can be performed from inside the Visual Studio Code plugin are:

CREATE TABLE

You can create the Oracle NoSQL Database table in two modes:

  1. Hover over the Oracle NoSQL Database connection to add the new table.

  2. Click the Plus icon that appears or right-click on the database connection name and click Create Table

    table-explorer

  3. In the Create Table page, select Simple DDL Input.

    Table - Create an Oracle NoSQL Database Table

    Field Description
    Table Name: Specify a unique table name.
    Column Name Specify a column name for the primary key in your table.
    Column Type Select the data type for your primary key column.
    Set as Shard Key Select this option to set this primary key column as shard key. Shard key is to distribute data across the Oracle NoSQL Database cluster for increased efficiency, and to position records that share the shard key locally for easy reference and access. Records that share the shard key are stored in the same physical location and can be accessed atomically and efficiently.
    Remove Click this button to delete an existing column.
    + Add Primary Key Column Click this button to add more columns while creating a composite (multi-column) primary key.
    Column Name Specify the column name.
    Column Type Select the data type for your column.
    Default Value (optional) Specify a default value for the column.

    Note: Default values cant be specified for binary and JSON data type columns.
    Not Null Select this option to specify that a column must always have a value.
    Remove Click this button to delete an existing column.
    + Add Column Click this button to add more columns.
    Unit Select the unit (Days or Hours) to use for TTL value for the rows in the table.
    Value Specify expiration duration for the rows in the table. After the number of days or hours, the rows expire automatically, and are no longer available. The default value is zero, indicating no expiration time.

    Note: Updating Table Time to Live (TTL) does not change the TTL value of any existing data in the table. The new TTL value applies only to those rows that are added to the table after this value is modified and to the rows for which no overriding row-specific value has been supplied.

  4. Click Create.

  5. You have an option to the view the DDL statement before and after creating a table.

    • Before creating the table - Click Show DDL in the Create Table screen to view the DDL statement formed based on the values entered in the fields in the Simple DDL input mode. This DDL statement gets executed when you click Create.

    • After creating the table - Right click on the existing table. Choose View Table DDL.

CREATE CHILD TABLE

To create a child table, right click on the desired table and choose Create Child Table. You can create a child table for an already existing Oracle NoSQL Database table in one of the two modes:

For more details on child tables, see Table Hierarchies in Oracle NoSQL Database Cloud Service Guide.

DROP TABLE

  1. Right-click the target table.

  2. Click Drop Table.

  3. Click Yes to drop the table.

CREATE INDEX

DROP INDEX

ADD COLUMN

DROP COLUMN

Freeze/UnFreeze Schema

To make a singleton table a Global Active table, you must first freeze the schema. For more information, see Freezing a table’s schema.

To Freeze/UnFreeze schema, follow the below steps:

  1. Right-click on the desired table, click Freeze/Unfreeze schema.

  2. A dialog box appears, click Yes, to confirm the action.

Manage Replicas

See Regional Table Replicas to understand what replicas are and how to convert a singleton table to a Global Active table.

Add Replicas

The Visual Studio Code plugin lets you to add a table replica in different regions. It also lets you add replicas to an existing Global Active table.

  1. Right-click on the desired table, from the Replicas section, select Add Replicas.

  2. From the Add Replica panel, select a region from the Replication region dropdown.

  3. Enter Read Capacity, Write Capacity, Disk Storagedepending on your requirements.

  4. Click Add Replica.

  5. When you receive a notification that replicas have been added, close the panel by clicking ‘x’ or pressing ‘Ctrl+F4’.

Drop Replicas

  1. Right-click on the desired table whose table replica you want to delete. From the Replicas sections, select Drop Replicas.

  2. From the Drop Regional Replicas panel, select the replica from the Replica Name dropdown you want to delete. To delete many replicas concurrently, click +Add, select the Replica Name.

    Note: To remove any replica, you wish not to delete, simply click Remove adjacent to the replica name.

  3. Click Drop Replicas.

  4. When you receive a notification that replicas have been dropped, close the panel by clicking ‘x’ or pressing ‘Ctrl+F4’.

View Replicas

  1. Right-click on the desired table to view its replicas. From the Replicas section, select View Replicas.

  2. In the View Regional Replicas panel, you can view a list of regional replicas with their Write Capacity.

  3. After viewing the replicas, close the panel by clicking ‘x’ or pressing ‘Ctrl+F4’.

Edit Reserved Capacity

  1. Right-click on the desired table and click Edit Reserved Capacity.

  2. In the Edit Reserved Capacity panel, you can update either the Provisioned Capacity or the On-Demand Capacity.

    1. Provisioned Capacity: You can edit the Read Capacity, Write capacity, and Disk Storage as per your requirements.

    2. On Demand Capacity: You can only modify the Disk Storage. The Read Capacity and Write Capacity are in Read-only mode.

  3. When you receive a notification that reserved capacity has been updated, close the panel by clicking ‘x’ or pressing ‘Ctrl+F4’.

Perform DML operations using Visual Studio Code

You can add data, modify existing data and query data from tables usingVisual Studio Code plugin.

Insert Data

Modify Data - UPDATE ROW/DELETE ROW:

Executing SQL Queries for a Table

Note: The dropdown will only show SQL statements related to the table you are dealing with.

Removing a Connection

Oracle NoSQL Database Connector provides two methods to remove a connection from Visual Studio (VS) Code.

You can:

Note: To remove a connection permanently from the plugin, select the connection from the Connections drop-down. Click Delete Connection. You get a confirmation to delete the plugin, click Yes to remove the connection from the plugin. Removing a connection from Visual Studio Code deletes the persisted connection details from the current workspace.

  1. Expand the TABLE EXPLORER pane in the left navigation if it’s collapsed.

  2. Right-click the connection you want to remove, then click Remove Connection.

  1. Open the Command Palette by pressing:

    • (Windows and Linux) Control + Shift + P

    • (macOS) Command + Shift + P

  2. From the Command Palette, select OracleNoSQL: Remove Connection.

    Note: Enter oraclenosql in the Command Palette to display all of the Oracle NoSQL DB commands you can use.

Authorization Requirements for Visual Studio Code

Learn about the authorization requirements needed in Oracle NoSQL Database Cloud Service to use Visual Studio Code.

The Visual Studio Code extension allows you to access Oracle NoSQL database Cloud Service using API-key authentication method. Access to resources in Oracle NoSQL Database Cloud Service such as tables, tablespaces, and APIs is managed through Identity and Access Management (IAM) policies. This ensures that only authenticated users, who are members of groups with the appropriate inspect, read, use, or manage table permissions in a given compartment, can interact with these resources. For more information, see Managing Access to NDCS Tables.

When using Visual Studio Code to manage tables in Oracle NoSQL Database Cloud Service tables, your effective IAM permissions determine which resources you can read from or write to. If a user attempts an action for which they lack authorization, the Visual Studio Code will return the corresponding authorization error as provided by OCI IAM.

For example, the OCI IAM denies any insert operation on an Oracle NoSQL Database Cloud Service table if your user group only has the “read” permission for NoSQL tables. The following error message is displayed in the Visual Studio Code extension:

Error Inserting the row : NoSQLError: [INSUFFICIENT_PERMISSION] Authorization failed or requested resource not found