How to find SQL Server running port?
Just to add — in recent versions it seems TCP is disabled by default in the Developer Edition, while UDP is on.
Nov 3, 2020 at 18:09
This is the one that works for me:
SELECT DISTINCT local_tcp_port FROM sys.dm_exec_connections WHERE local_tcp_port IS NOT NULL
7,590 2 2 gold badges 37 37 silver badges 46 46 bronze badges
answered Feb 5, 2014 at 19:14
Stefan Steiger Stefan Steiger
79.3k 66 66 gold badges 381 381 silver badges 442 442 bronze badges
Aug 25, 2021 at 9:40
very simple. make a note of the sqlsrvr.exe PID from taskmanager then run this command:
netstat -ano | findstr *PID*
it will show TCP and UDP connections of your SQL server (including ports) standard is 1433 for TCP and 1434 for UDP
example :
18.1k 7 7 gold badges 81 81 silver badges 90 90 bronze badges
answered Jun 19, 2013 at 10:06
mantas mileris mantas mileris
811 6 6 silver badges 2 2 bronze badges
This worked for me «in reverse»: needed to find (non-default) port number of remote machine that I was connected to in SSMS.
May 25, 2016 at 19:44
If you can start the Sql Server Configuration Manager > SQL Server Network Configuration > Your instance > TCP/IP > Properties

answered Aug 3, 2015 at 15:06
abedurftig abedurftig
1,118 1 1 gold badge 12 12 silver badges 24 24 bronze badges
If you have run «netstat -a -b -n» (from an elevated command prompt) and you don’t see «sqlservr.exe» at all then either your SQL Server service is not running or its TCP/IP network library is disabled.
Run SQL Server Configuration Manager (Start | All Programs | Microsoft SQL Server 2008 | Configuration Tools).
Navigate to SQL Server Services. In the right-hand pane look for SQL Server (). Is it stopped? If so, start it.
Navigate to SQL Server Network Configuration (or SQL Server Network Configuration (32-bit) as appropriate) then Protocols for . In the right-hand pane look for «TCP/IP». Is it disabled? If so, enable it, then restart the SQL Server service.
Note that he Instance ID will be MSSQLSERVER for the default instance.
Please also note that you don’t have to enable the TCP/IP network library to connect a client to the service. Clients can also connect through the Shared Memory network library (if the client is on the same machine) or the Named Pipes network library.
answered Mar 11, 2013 at 2:29
Greenstone Walker Greenstone Walker
1,090 9 9 silver badges 8 8 bronze badges
If you don’t want to look in SQL Server Management (sqlservermanager15.msc), then run this query in the database, e.g. from sqlcmd or ssms:
SELECT * FROM [sys].[dm_tcp_listener_states]
| listener_id | ip_address | is_ipv4 | port | type | type_desc | state | state_desc | start_time |
|---|---|---|---|---|---|---|---|---|
| 1 | ::1 | False | 1433 | 0 | TSQL | 0 | ONLINE | 2021-01-01 00:00:00.000000 |
| 2 | 127.0.0.1 | True | 1433 | 0 | TSQL | 0 | ONLINE | 2021-01-01 00:00:00.000000 |
Thanks to @vladimir-bashutin for pointing out this one. Here is another one:
SELECT [name] ,[protocol_desc] ,[type_desc] ,[state] ,[state_desc] ,[is_admin_endpoint] FROM [master].[sys].[endpoints]
| name | protocol_desc | type_desc | state | state_desc | is_admin_endpoint |
|---|---|---|---|---|---|
| TSQL Local Machine | SHARED_MEMORY | TSQL | 0 | STARTED | False |
| TSQL Named Pipes | NAMED_PIPES | TSQL | 0 | STARTED | False |
| TSQL Default TCP | TCP | TSQL | 0 | STARTED | False |
| TSQL Default VIA | VIA | TSQL | 0 | STARTED | False |
So now you have the port and protocol. If you don’t have access to these system tables, consider using an SSRP client, such as https://github.com/adzm/ssrpc.
answered Sep 3, 2021 at 16:53
63 1 1 silver badge 5 5 bronze badges
Maybe it’s not using TCP/IP
Have a look at the SQL Server Configuration Manager to see what protocols it’s using.
answered Sep 6, 2012 at 10:02
51k 7 7 gold badges 99 99 silver badges 105 105 bronze badges
SQL Native Client config? TCP/IP is Enabled. But default port is set to 1433 :/
Sep 6, 2012 at 10:14
@keram No — that’s for clients. You want the server configuration utiltiy.
Sep 6, 2012 at 10:18
where I can find that config?
Sep 6, 2012 at 10:20
On the start menu — msdn.microsoft.com/en-us/library/ms174212(v=sql.100).aspx
Sep 6, 2012 at 10:22
USE master DECLARE @portNumber NVARCHAR(10) EXEC xp_instance_regread @rootkey = 'HKEY_LOCAL_MACHINE', @key = 'Software\Microsoft\Microsoft SQL Server\MSSQLServer\SuperSocketNetLib\Tcp\IpAll', @value_name = 'TcpDynamicPorts', @value = @portNumber OUTPUT SELECT [Port Number] = @portNumber GO
4,492 10 10 gold badges 23 23 silver badges 48 48 bronze badges
answered Jul 6, 2018 at 12:08
287 3 3 silver badges 10 10 bronze badges
This is another script that I use:
-- Find Database Port script by Jim Pierce 09/05/2018 USE [master] GO DECLARE @DynamicportNo NVARCHAR(10); DECLARE @StaticportNo NVARCHAR(10); DECLARE @ConnectionportNo INT; -- Look at the port for the current connection SELECT @ConnectionportNo = [local_tcp_port] FROM sys.dm_exec_connections WHERE session_id = @@spid; -- Look for the port being used in the server's registry EXEC xp_instance_regread @rootkey = 'HKEY_LOCAL_MACHINE' ,@key = 'Software\Microsoft\Microsoft SQL Server\MSSQLServer\SuperSocketNetLib\Tcp\IpAll' ,@value_name = 'TcpDynamicPorts' ,@value = @DynamicportNo OUTPUT EXEC xp_instance_regread @rootkey = 'HKEY_LOCAL_MACHINE' ,@key = 'Software\Microsoft\Microsoft SQL Server\MSSQLServer\SuperSocketNetLib\Tcp\IpAll' ,@value_name = 'TcpPort' ,@value = @StaticportNo OUTPUT SELECT [PortsUsedByThisConnection] = @ConnectionportNo ,[ServerStaticPortNumber] = @StaticportNo ,[ServerDynamicPortNumber] = @DynamicportNo GO
Порты TCP и UDP для SQL Server
Подсистемы и компоненты, которыми компания Microsoft продолжает дополнять SQL Server, заметно увеличили число сетевых подключений, используемых платформой. Иногда сложно определить, какие порты брандмауэра открыты для каждого компонента SQL Server. Чтобы упростить задачу, мы подготовили список широко применяемых сетевых портов SQL Server
Из простой реляционной системы управления базами данных SQL Server превратилась в многоцелевую платформу данных корпоративного уровня. .
TCP 1433 — порт, выбираемый для SQL Server по умолчанию. Это официальный номер сокета IANA (агентство по выделению имен и уникальных параметров протоколов Интернета) для SQL Server. Клиентские системы используют порт TCP 1433 для подключения к системе управления базами данных; в среде SQL Server Management Studio (SSMS) порт служит для управления экземплярами SQL Server через сеть. Можно настроить SQL Server для прослушивания другого порта, но в большинстве случаев используется порт 1433.
TCP 1434 — порт, выбираемый по умолчанию для выделенного административного соединения. Вы можете запустить выделенное административное соединение с помощью командной строки sqlcmd или введя «ADMIN:» с последующим именем сервера в диалоговом окне SSMS Connect to Database Engine.
Порт UDP 1434 используется для именованных экземпляров SQL Server. Служба SQL Server Browser прослушивает этот порт, чтобы обнаружить входящие соединения с именованным экземпляром. Затем служба передает клиенту номер TCP-порта для запрошенного имени экземпляра.
TCP 2383 — порт, выбираемый по умолчанию для служб SQL Server Analysis Services.
TCP-порт 2382 используется для запросов подключения к именованному экземпляру Analysis Services. Как и в случае с реляционной базой данных и портом UDP 1434, служба SQL Server Browser прослушивает порт TCP 2382, обнаруживая запросы для именованных экземпляров Analysis Services. Затем службы Analysis Services перенаправляют запрос в соответствующий порт для именованного экземпляра.
У TCP-порта 135 несколько применений. Он используется отладчиком Transact-SQL, а также применяется для запуска, останова и управления службами SQL Server Integration Services, хотя необходимость в нем возникает только при подключении к удаленному экземпляру службы из SSMS.
TCP-порты 80 и 443 чаще всего используются для доступа к серверу отчетов. Однако они поддерживают и URL-запросы к SQL Server и Analysis Services. TCP 80 — стандартный порт для HTTP-соединений, использующих URL. TCP 443 обслуживает HTTPS-соединения через протокол SSL.
Неофициальные TCP-порты
Компания Microsoft использует TCP-порт 4022 для экземпляров SQL Server Service Broker в электронной документации SQL Server. Аналогично, экземпляры BOL Database Mirroring задействуют TCP-порт 7022.
В этом списке перечислены самые необходимые порты. Более подробные сведения о портах TCP и UDP, используемых SQL Server, приведены в статье Microsoft «Configure the Windows Firewall to Allow SQL Server Access» (msdn.microsoft.com/en-us/library/cc646023%28v=sql.120%29.aspx).
[РЕШЕНО] Внешнее подключение к MSSQL
Собственно не могу подключиться к MSSQL серверу по ODBC через 1с
Может кто знает куда копать ? как починить.
Administrator
Сообщений: 721 Баллов: 8901 Рейтинг: 0 Регистрация: 09.02.2011
20.11.2019 19:44:35
Попробую по пунктам описать куда копать:
1. стандартный порт для подключение по ODBC 1433 проверяем висит ли что то на этом порту:
netstat -an | find»1433″
2. Если да то копаем в сторону фаервола. разрешаем правила — либо целиком отключаем:
Если у вас включен Windows Firewall (или любой другой), необходимо открыть порт 1433
Если нетстат показывает что ничего не висит на 1433 то проверяем по пунктам:
1. Запускаем SQL Server Configuration Manager
В окне конфигурации SQL Server выберите ветку Network Configuration SQL Server -> Протоколы для SQL Server. Затем включите необходимые порты. Обычно достаточно TCP/IP.
— также в этом окошке откройти закладку ip adresses — и там в самом низу порт — он может быть не стандартный. (подключаться надо на него)
После этого перейдите в ветку Настройка собственного клиента SQL Клиентские протоколы. Произведите настройку необходимых протоколов. Обычно достаточно TCP/IP с настройками по умолчанию. Если вы измените номер порта, его нужно будет разблокировать в файрволе, а также указывать при соединении с SQL сервером. Рекомендуется оставить номер порта по умолчанию – 1433
2. После конфигурации протоколов, перейдите в ветку «Службы SQL Server». Перезапустите SQL Server.
3. Запустите Microsoft SQL Server Management Studio (среду управления сервером баз данных) и подключитесь к серверу. Кликните правой кнопкой мышки по серверу. В появившемся меню выберите «Свойства».
— В разделе «Безопасность» поставьте «Проверка подлинности SQL Server и Windows».
— В разделе «Соединения» установите опцию «Разрешить удаленные соединения с этим сервером».
ПЕРЕЗАПУСТИТЕ СЛУЖБУ SQL SERVERA.
ВОЗМОЖНО КОМУ ТО ПОМОЖЕТ: Фактический порт TCP для подключения через ODBC можно найти в реестре по адресу HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\\MSSQLServer\SuperSocketNetLib\Tcp
Услуги Системного Администратора — Работаю только с Юр. Лицами по договору обслуживания.
Administrator
Сообщений: 721 Баллов: 8901 Рейтинг: 0 Регистрация: 09.02.2011
20.11.2019 20:04:49
И еще раз я об этом написал с самого начала, с чего стоит копать, стандартный порт подключения 1433
т.е мы на самом сервере должны понять.
1. Запустите NETSTAT -A чтобы просмотреть список открытых портов (скажем, LISTENING). Если 1433 нет среди них, то SQL-сервер не работает или не прослушивает этот порт.
2. Если в списке указано 1433, проверьте локальный брандмауэр, чтобы узнать, разрешает ли он подключение к/из локального хоста и/или разрешает подключения к 1433.
3. Вы можете попробовать TELNET 1433 (к локал хост и к внешнему ip с другово клиент)
Услуги Системного Администратора — Работаю только с Юр. Лицами по договору обслуживания.
Administrator
Сообщений: 721 Баллов: 8901 Рейтинг: 0 Регистрация: 09.02.2011
20.11.2019 20:16:18
Что делать если вы не видите открытый стандартный порт 1433, способы понять, какой порт использует ваш MSSQL
1. через (SQL Server Configuration Manager) — описал в самом первом посте и в посте ниже — этого.
2. через логи событий
3. SQL Server Error Logs
4. через выполнение SQL запроса.
5. через реестр — описал в первом ответе
—- описание всех способов:
By default SQL Server listens on TCP port number 1433, and for named instances TCP port is dynamically configured. There are several options available to get the listening port for SQL Server Instance.
Here are a few methods which we can use to get this information.
Method 1: SQL Server Configuration Manager
Method 2: Windows Event Viewer
Method 3: SQL Server Error Logs
Method 4: sys.dm_exec_connections DMV
Method 5: Reading registry using xp_instance_regread
Let’s see how you can use each of these methods in detail:
Method 1: SQL Server Configuration Manager:
Step 1. Click Start > All Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager
Step 2. Go to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for
Step 3. Right Click on TCP/IP and select Properties
Step 4. In TCP/IP Properties dialog box, go to IP Addresses tab and scroll down to IPAll group.
If SQL Server if configured to run on a static port it will be available in TCP Port textbox, and if it is configured on dynamic port then current port will be available in TCP Dynamic Ports textbox. Here my instance is listening on port number 61499.
Method 2: Windows Event Viewer:
When SQL Server is started it logs an event message as ‘Server is listening on [ ‘any’ ‘ in windows event logs. Here will be actual port number on which SQL Server is listening.
To view this using Event Viewer:
Step 1. Click Start > Administrative Tools > Event Viewer.
Note: If Administrative Tools are not available on Start menu, go to Start > Control Panel > System and Maintenance > Administrative Tools > View event logs
Step 2. Navigate to Event Viewer > Windows Logs > Application
Step 3. Since huge amount of event are logged, you need to use filtering to locate the required logs. Right click on Application and select Filter Current Log…
Step 4. You can filter the events by Event ID and Event source. The event we are interested in has Event ID of 26022, and it’s source is SQL Server Instance. You need to filter by both Event ID and SQL Server Instance if you have multiple instances installed, for a single instance you can filter by Event ID only. Click on OK to apply the filter.
Step 5. Once the filter is applied, Locate message ‘Server is listening on [ ‘any’ …’. As we can see from below screenshot that SQL Server Instance is running on TCP Port 61499.
Method 3: SQL Server Error Logs:
When SQL Server is started it also logs an message to SQL Server Error Logs. You can search for port number in SQL Server Error Logs by opening SQL Server Error Log in notepad or via T-SQL using extended stored procedure xp_ReadErrorLog as below:
EXEC xp_ReadErrorLog 0, 1, N’Server is listening on’, N’any’, NULL, NULL, ‘DESC’
LogDate ProcessInfo Text
2013-03-21 13:34:40.610 spid18s Server is listening on [ ‘any’ 61499].
2013-03-21 13:34:40.610 spid18s Server is listening on [ ‘any’ 61499].
(2 row(s) affected)
As we can see from the output that SQL Server Instance is listening on 61499.
Note: This method does not work if SQL Server Error Logs have been cycled. See sp_Cycle_ErrorLog for more information.
Method 4: sys.dm_exec_connections DMV:
DMVs return server state that can be used to monitor SQL Server Instance. We can use sys.dm_exec_connections DMV to identify the port number SQL Server Instance is listening on using below T-SQL code:
WHERE session_id = @@SPID
(1 row(s) affected)
As we can see from the output… same as above Smile
Method 5: Reading registry using xp_instance_regread:
Port number can also be retrieved from Windows Registry database.
We can use extended stored procedure xp_instance_regread to get port number information using below T-SQL code:
DECLARE @portNumber NVARCHAR(10)
‘Software\Microsoft\Microsoft SQL Server\MSSQLServer\SuperSocketNetLib\Tcp\IpAll’,
@value = @portNumber OUTPUT
SELECT [Port Number] = @portNumber
(1 row(s) affected)
As we can see … same as above Smile Smile
Note: The above code will only work if SQL Server is configured to use dynamic port number. If SQL Server is configured on a static port, we need to use @value_name = ‘TcpPort’ as opposed to @value_name = ‘TcpDynamicPorts’.
Hope This Helps!
Услуги Системного Администратора — Работаю только с Юр. Лицами по договору обслуживания.
Administrator
Сообщений: 721 Баллов: 8901 Рейтинг: 0 Регистрация: 09.02.2011
20.11.2019 20:20:44
Статические и динамические порты SQL Server

Microsoft SQL Server может работать в двух режимах:
Прослушивание одного порта (по-умолчанию это TCP порт 1433). Этот режим будет выбран по-умолчанию, если во время установки SQL Server не использовать именованный экземпляр.
Динамический выбор портов. В этом случае при запуске SQL Server выберет свободный порт. Этот режим будет выбран по-умолчанию, если во время установки SQL Server настроить на использование именованного экземпляра.
Для того чтобы определить и изменить режим работы SQL Server нужно:
Открыть «Диспетчер конфигурации SQL Server»
В левом столбце выбрать «Сетевая конфигурация SQL Server» -> «Протоколы для «
В правом столбце дважды кликнуть по протоколу TCP/IP
В открывшемся окне в разделе IPAll указано два параметра:
«TCP порт» — при помощи этого параметра можно задать статический порт. По-умолчанию значение 1433.
«Динамические TCP порты» — при помощи этого параметра можно задать диапазон, из которых будет выбираться порт для SQL Server
Услуги Системного Администратора — Работаю только с Юр. Лицами по договору обслуживания.
Administrator
Сообщений: 721 Баллов: 8901 Рейтинг: 0 Регистрация: 09.02.2011
02.12.2019 15:33:55
Для своей работы система с сервером 1С использует следующие порты:
1433 (TCP/IP) — сервер SQL;
1434 (UDP) — сервер SQL;
1540 (TCP/IP) — агент сервера (если сервер один, то можно не открывать);
1541 (TCP/IP) — менеджер кластера;
диапазон 1560-1591 (TCP/IP) — процесс 1С;
475 (TCP/IP) — HASP-менеджер;
475 (UDP) — HASP-менеджер;
Пример запуска 1С из командной строки:
«C:\Program Files\1cv8\8.3.12.1529\bin\ragent.exe» -srvc -agent -regport 1541 -port 1540 -range 1560:1591 -debug -d «C:\Program Files\1cv8\srvinfo»
Troubleshooting: Enabling TCP/IP in the SQL Server
TCP/IP must be enabled for users who are running SQL server on their workstations.
Note: Users with SQL Server 2012 installed, SQL Server Network Configuration can now be accessed via Control Panel > Administrative Tools > Computer Management.
Enable TCP/IP in the SQL Server

- From the Start menu, click on All Programs.
- Click on Microsoft SQL Server 20XX.
- Expand the Configuration Tools subfolder and right-click on SQL Server Configuration Manager. Click on Run as Administrator.
- Select SQL Server Network Configuration and click Protocols for SMTKINGDOM.
- In the right pane, right-click TCP/IP and click Enable.
Restart SQL Server

In order for the changes to take effect, you need to restart the server.
- Open the Control Panel from the Start menu.
- Click on System and Security.
- Select Administrative Tools.
- Double-click Services to open the Services window.
- Scroll down and right-click on the SQL Server (SMTKINGDOM)** instance and select Restart.
Note: Make sure all programs using the SQL instance are closed before you restart.
** The instance can have any name applied. For users with Kingdom already installed the instance name will be, by default, SMTKINGDOM. Users with a fresh Insight install will be named DUGINSIGHT.
- Prev:Manually Attaching Kingdom SQL Database
- Next:Troubleshooting: Windows services SQL Server (SMTKINGDOM) and SQL Server Browser Are Running
Topics
- Introduction 6
- About Insight
- What’s new in 2022?
- What’s new in DUG Insight 5.1
- What’s new in DUG Insight 4.9
- What’s new in DUG Insight 4.8
- How to Use this Manual (web)
- System Requirements
- System Requirements (Processing & Imaging)
- Video Card Requirements
- Downloading Insight and Installing on Windows
- Running Insight on macOS
- Installing on Linux
- Upgrading
- Operating Systems and Storage Drive Format
- Introduction to the IT / Data Manager Guide
- Overview of an Insight Project
- Filesystem
- Network/Multi-User
- Backup and Restore
- Manually closing Insight in Microsoft Windows
- How DUG access data: random, concurrent, or STREAM (large data)
- Licencing Overview
- Obtaining a Trial Licence
- Online Activation
- Email Activation
- Free Academic Licence
- Viewing Licences
- Configuring Proxy Settings
- Firewall Configuration
- Modules in Insight
- Insight (features)
- Explorationist (features)
- Gather Attributes (features)
- Pore Pressure Prediction (features)
- Rock (features)
- Lithofluids (features)
- Link to Kingdom and Petrel
- Launching Insight
- Allocating Memory
- Creating a Project
- Opening an Existing Project
- Configure a Project
- How it Works (Units)
- Using Sample Data
- Viewing and Sending Diagnostic Logs
- Configuring 4k Monitors in Insight
- Project Database Overview
- Project vs Session
- Autosave in Insight
- Multi-user Considerations
- Loading Items Already in the Project
- Deleting an Item
- Importing Items into the Project
- Using the Text Importer
- Using and Managing Sessions
- Missing Files
- Importing a Session
- About the Control Panel
- Control Panel Shortcuts
- Working with Control Panel folders
- Creating/Importing an Item
- Moving an Item
- Sorting Items
- Activating/Deactivating Items
- Displaying the Details Panel
- Switching between horizontal and vertical panel
- File Menu
- Hotkeys
- Tool Menu
- Preferences
- View Menu and Displays
- Window Menu
- Available Help Resources
- Insight User Manual (Help)
- Online Video Tutorials (Help)
- Sending Feedback (Help)
- Licence Manager (Help)
- Viewing Software Information (Help)
- Viewing System Information (Help)
- Checking for Updates (Help)
- Disabling Automatic Update Check
- Sending Logs (Help)
- Survey Overview
- Creating a Survey
- Loading a Survey
- Importing a Survey
- Defining Survey Details
- Exporting a Survey
- Repositioning and Redefining Surveys
- Replacing 2D Survey Geometry
- Defining and Configuring 3D Surveys
- Survey File Examples
- SEG-Y Loader Overview
- Launching SEG-Y Loader
- Basic Settings (3D SEG-Y)
- Selecting Files (3D SEG-Y)
- Specifying Header Locations (3D SEG-Y)
- Investigating Headers (3D SEG-Y)
- Filtering (3D SEG-Y)
- Analysing (3D SEG-Y)
- Defining a Survey (3D SEG-Y)
- Output and Writing Options (3D SEG-Y)
- Writing (3D SEG-Y)
- Launching SEG-Y Loader
- Basic Settings (2D SEG-Y)
- Selecting Files (2D SEG-Y)
- Specifying Header Locations (2D SEG-Y)
- Investigating Headers (2D SEG-Y)
- Filtering (2D SEG-Y)
- Analysing (2D SEG-Y)
- Loading Navigation Data Files
- Defining a Survey (2D SEG-Y)
- Output and Writing Options (2D SEG-Y)
- Writing (2D SEG-Y)
- Importing ASCII Volume
- Selecting Files (ASCII Volume)
- Specifying Keywords and Data Locations (ASCII Volume)
- Analysing (ASCII Volume)
- Defining a Survey (ASCII Volume)
- Output and Writing Options (ASCII Volume)
- Writing (ASCII Volume)
- Working with 2D Surveys
- Managing a 2D Line Set
- Displaying in Map View (2D Data)
- Viewing Selected 2D Lines in 3D View
- Viewing Lines in Multiple 2D Line Views
- Exporting 2D Line Sets
- Viewing Multiple 2D Volumes
- Refreshing 2D Volumes
- Coordinate Reference System Overview
- Converting CRS When Importing a Survey
- Converting CRS When Importing an XY Horizon
- Converting CRS When Importing a Fault
- Converting CRS When Importing a Well
- Converting CRS When Importing an Arbline
- Converting CRS When Importing a Map Polygon
- Converting CRS When Importing a Mute
- Converting CRS When Importing a Wavelet Field
- Converting the CRS when importing culture
- How do I create a custom coordinate reference system (CRS)?
- Views Overview
- Navigation Bar in Views
- Information Bar
- Zooming (Section Views)
- Settings for Section Views
- Taking Screen Captures
- Using Snapshots
- Displaying Images as Map Slices
- Displaying Header Graphs (on sections)
- Displaying Horizontal Grid Lines (on sections)
- Displaying Shotpoint Data for 2D Lines
- Displaying Scanned Seismic (on sections)
- Using the Headers View
- Using the Comparison Slider
- Using the Measuring Tool
- Using the Gather Picking Panel
- Using XHair Values
- Product Extents Table
- Linking Multiple Views
- Opening Multiple Views
- Using the Arbline View
- Using the Arbline SD View
- Using the IL/CL View
- Opening a Gather View
- Using the IL/Gather/CL View
- Using the 2D Line View
- Using the 2D Gather View
- Using the 2D Line SD View
- Custom Annotations (Section Views)
- Using the Map View
- Viewing Surveys (Map View)
- Volumes and Horizons (Map View)
- Customising the Map View
- Contouring (Map View)
- Creating Polygons from Contours
- Creating Polygons from Horizons
- Custom Map Annotations
- Measuring (Map View)
- Defining Map View Display Settings
- Horizon Operations
- Adding data intersections in Map View
- Exporting Georeferenced Images from Map View
- Posting Well Information in the Map View
- Using the 3D View
- Defining 3D View Settings
- 3D Volume Visualisation
- Contours in 3D Viewer
- Horizon Options in 3D View
- Displaying 2D Lines (3D View)
- Using the Animation Timeline Editor
- Classes and Colourbars Overview
- Assigning Class (Overview)
- Creating a Class
- Editing a Class
- Creating a New Colourbar
- Editing a Colourbar
- Importing a Colourbar
- Exporting a Colourbar
- Modifying a Colourbar .ducolbar File
- Modifying a Colourbar .ducb File
- Configuring Colour Bar Annotations
- Cycling through colourbars
- Volume and Display Interpolation Methods
- Opacity
- Adjusting the Clip
- Defining Line Settings
- Defining Wiggle Settings
- Defining Track View Settings
- Colourbar naming convention
- Volumes Overview
- Adding Volumes (to session)
- Importing Volumes
- Optimising Volumes for Performance
- Changing a Volume’s Class
- Volume Display Settings
- Copying Volumes
- Deleting Volumes
- Redefining Volume’s Survey
- Exporting to DUGIO
- Exporting to Text
- Exporting to SEG-Y
- Exporting Compressed Gathers
- Editing SEG-Y headers
- Setting SEG-Y binary headers (export)
- Setting SEG-Y trace headers (export)
- Setting the SEG-Y text (EBCDIC) header (export)
- Horizon Overview
- Creating a Horizon
- Horizon Undo and Redo
- Loading Horizons
- Context Menu (Horizon)
- Horizon Details and Configuration
- Multi-survey Horizons
- Copying a Horizon
- Redefining Horizon Survey
- Redefining Horizon Display Settings
- Updating Class Settings of Multiple Horizons
- Manual Picking (Horizon)
- Propagating a Horizon
- Configuring Gather Horizons
- Erasing a Horizon
- Displaying Adjacent Horizon Picks
- Surface Groups
- Using Custom Properties
- Custom Horizon Properties
- Using Horizon Properties
- Horizon Display and Amplitude Extraction
- Structural Curvature for Horizons
- Displaying Horizon Histograms
- Working with Horizon Colourbars
- Importing a Horizon
- Using the Horizon Text Importer
- Import Formats (Horizon)
- Exporting a Horizon
- Export Formats (Horizon)
- Exporting Multiple Horizons
- Horizon Operations in Map View
- Horizon Amplitude Extraction
- Derivative Filter (Horizon)
- Erase (Horizon)
- Extract (Horizon)
- Gather Amplitude Operation
- Ghost (Horizon)
- Header Extraction
- Horizon Maths
- Common Horizon Tasks (Horizon Maths)
- Interpolate/Extrapolate (Horizon)
- How Interpolation Settings Work
- Regrid (Horizon)
- Smooth (Horizon)
- Snap (Horizon)
- Create Horizon from Well Markers
- Create Constant Horizon
- Create Gather Horizon from Non-Gather Horizon
- Creating Groups
- Copying Groups
- Viewing a Volume Group
- Enabling/Disabling with Groups
- Display Groups
- RGB and CMY Groups
- Selection Groups
- Co-rendering Multiple Volumes
- Panel Groups
- Faults Overview
- Viewing Faults
- Context Menu (Fault)
- Picking Faults
- Working with Unassigned Fault Sticks
- Assigning/Unassigning Fault Sticks
- Bulk Operations on Fault Sticks
- Importing a Fault
- Exporting a Fault
- Wells Overview
- Creating a New Well
- Well Settings and Display
- Defining Well Path
- Defining Markers (Wells)
- Defining Time/Depth Pairs (Wells)
- Defining Log Curves
- Selecting Default Components (Wells)
- Using Multiple Log Curve Files (Wells)
- Managing Well Components
- Editing Well Components
- Assigning Classes and Units to Well Curve
- Importing a Legacy Well
- Import Formats (Wells)
- Importing Bulk Well Data
- Adding Wells (to session)
- Picking Well Markers
- Exporting Basic Well Information
- Exporting Bulk Well Data
- Exporting Traces Along Well Path
- Exporting Well Checkshots
- Exporting Well Deviations
- Exporting Well Markers
- Exporting Log Curves
- Exporting Well to Shapefile and Kml/Kmz files
- Working with Well Markers and Tops
- Taking Ownership of Wells
- Well Display in Sections and 3D
- Well Correlation and Single Well View
- Using the Well Correlation View
- Using the Single Well View
- Working with Templates
- Well View Settings
- Markers and Horizons in Well Displays
- Tracks Overview
- Adding Seismic or Gather Tracks
- Using the Well Connection Track
- Curve Tracks
- Curve Display Settings
- Well Log Curves
- Volumes as Curves
- Crossover Fill Curves
- Stacked Fill Curves
- Overlaying wells on Seismic/Gather Tracks
- Editing Markers (Well Correlation View)
- Selecting Well Curves
- Time-Depth Conversion with Wells
- Crossplot highlights in Well Views
- Creating a Probe
- Creating an Arbline
- 2D Arbline Picking
- Editing an Arbline
- Moving an Arbline
- Viewing Data Along Arbline
- Importing an Arbline
- Exporting an Arbline
- Polygon Overview
- Creating a Polygon
- Editing a Polygon
- Picking in Map View (Polygon)
- Picking in IL/CL View (Polygon)
- Picking in 3D View (Polygon)
- Picking in Arbline View (Polygon)
- Using Fault Polygons
- Using Correlation Polygons
- Polygon Operations
- Exporting a Polygon
- Importing Polygons
- Using Tables
- Create New Table
- Using Table Maths
- Exporting Table
- Using Table to Overlay Views
- Crossplots (Overview)
- Configuring Crossplots
- Highlighting crossplot points (from sections)
- Using Litho-Fluid Models
- Highlighting geobodies (from crossplots)
- Crossplot polygon points (example export)
- Using Multiple Well Crossplots
- Display Trends and Regression in Crossplots
- Manual Picking (Mute)
- Creating an Angle Mute
- Exporting Mute
- Creating a Mute Table
- Working with Culture
- Importing Culture Files
- Importing Non-Georeferenced Image Files
- Importing Bubble Map
- Configuring Bubble Map
- Draping Culture on Horizon
- Create a Prior Model
- Importing a LithoFluid Model/PDF
- Using Rock-Physics Trends
- QI Workbench Overview
- Using the QI Workbench Window
- Loading a Trend File
- Creating Fluid Composite
- Creating Lithologies Composite
- Creating Litho-Fluids
- Creating Interfaces
- Using the Probabilities Tab
- Reflectivity and Separability
- Generating a Litho-fluid Model
- Generating an Interface Model
- Wavelet Overview
- Creating a Wavelet Field
- Importing a Wavelet
- Location/Time-Specific Wavelet
- Configuring the Wavelet Preview Window
- Statistical Wavelet Extraction
- Creating a Windowing Model
- Converting Time-Depth
- How it Works (Time-Depth Conversion)
- Interval velocity posting convention
- Processes Overview
- Processes in Insight
- Anisotropic Model Conversion
- Angle Gathers
- Angle Stacks
- Assign Header Values
- Attribute Maps
- Attribute Maps Stack
- Autocorrelation
- Automatic Gain (AGC)
- AVA Stack Rotation
- AVO Polynomial Fit
- Band-Pass Filter
- Body Detection
- Cadzow Filter
- Composite QC
- Convolution
- Create Gathers
- Constrained Simultaneous Inversion (Absolute)
- Constrained Simultaneous Inversion (Relative)
- Correlation (Similarity)
- Cross Correlation 2D
- Cross Correlation
- Curvature (Process)
- Deconvolution
- Delta Model
- Despike
- Detect Mute
- Directional Correlation (Similarity)
- Dip Azimuth
- Dip Field
- Dip Filter
- Edges
- Enhance Flat
- F-K Transform
- F-X Transform
- Flattener
- Frequency-Domain Radon
- Frequency Split
- FX Deconvolution
- Gain
- Header and Trace Interpolation
- Header Maths
- Header Sequence Builder
- Hi-Res Radon Transform
- Incoherence
- Instantaneous Attributes
- Intercept and Gradient
- K Filter
- LF Model (End Member Trends)
- LF Model (Ghost Horizon)
- LF Model (Simple Kriging)
- Linear Moveout Correction (LMO)
- Linear Noise Removal (LNR)
- LithoFluid Probability
- Local Trace Alignment
- Match
- Minimum Phase
- Mute Gathers
- NaN Removal
- Normal Moveout Correction
- Partial Binning/Stacking
- Phase Rotation
- Pick Multiple Horizons
- Picked Function Model
- Plane Wave Dip Filter
- Polygon Mute
- Pore Pressure: Density Volume
- Pore Pressure: Eaton Pressure Volume
- Pore Pressure: Miller (No Unloading) Pressure Volume
- Posting Convention Conversion
- Q Filter
- Q Estimation
- Q Conversion
- Reassign Geometry Headers
- Reassign SCALCO/SCALEL Headers
- Restore Mute
- RMO Correction
- Semblance (Similarity)
- Semblance (Velocity)
- Simple Mute
- Simple Structured Model
- Spectral Decomposition
- Spectral Shaping
- Trace Chooser
- Stacking
- Structurally-Oriented Filter
- Tau-P Mute
- Time-Frequency Denoise (TFDN)
- Trace Header Variables for Math Expressions
- Trace Mix
- Trace Padding
- Trace Shift
- Trim Statics
- True-Amplitude Frequency Equalisation (TAFE)
- V0 from Delta and Isotropic Depth Mig Velocities
- Velocity Conversion
- Velocity Model (From Well Checkshots)
- Volume No-Decrease
- Velocity Re-Datum
- Volume Combine
- Volume CRS Conversion
- Volume Derivative
- Volume Integration
- Volume Interpolation/Extrapolation
- Volume Maths
- Volume Maths (Simple)
- Functions and Variables for Math Expressions
- Using Math Template
- Volume Merge
- Volume Resampling
- Volume Sculpting
- Volume Smoothing
- Volume Sort (Records)
- Volume Swap
- Wavelet Transform
- Zero Phase
- Using Workflows
- Submitting Workflows to the Local Job Scheduler for Windows
- Managing Submitted Workflows
- Managing Jobs via the Cluster Monitor
- Troubleshooting Workflow Submission Issues
- Using Well Processes
- Curve Extrapolator
- Curve Filter
- Curve Maths
- Curve Maths (Simple)
- Elastic Properties (Isotropic)
- Fluid Property Calculator
- Reflectivity (Stack & Gather)
- Vs or Density (from Vp)
- Synthetics (Stack & Gather)
- Thickness Calculator
- Create Episode for RMO picking
- Parabolic RMO Picking
- Non-Parabolic RMO Picking
- Effective Eta Picking
- Configuring Display Settings (RMO)
- Using the Volumetrics Wizard
- Defining Volumetrics Parameters
- Manual Mistie Corrections
- Manual Mistie Corrections (Overview)
- Manual Mistie Corrections (2D)
- Manual Mistie Corrections (3D)
- Automatic Mistie Corrections
- How it Works (Automatic Mistie)
- Viewing Mistie Summary
- Velocity Picking Overview
- Create a Velocity Picking
- Using the Velocity Picking Window
- Configuring the Velocity Picker
- Configuring the Semblance
- Interpolation/Extrapolation (Velocity Picking)
- Stacking (Velocity Picking)
- Configuring Display Settings (Velocity Picking)
- Picking the Velocity
- Exporting/Importing Velocity Picks
- Synthetics Overview
- Using the Synthetics Window
- Creating Synthetic Cases
- Defining Log Curves (Synthetics)
- Applying Sequential Backus Averaging
- Overriding Wavelets
- Overriding the Display Window
- Overriding the Window of Interest
- Editing Time/Depth Pairs (Synthetics)
- Working with Time-Depth Sets and Checkshots
- Manually Create T-D Pairs
- Resampling Time-Depth Pairs
- Generating T-D Pairs from another well
- Displaying the Velocity Model Curve
- Generating T-D Pairs from Sonic Log
- Generating T-D Pairs from Velocity Model
- Defining View Settings (Synthetics)
- Displaying the Delta Curve
- Displaying the Drift Curve
- Displaying the Correlation Curve
- Statistical Analysis of Synthetics
- Exporting Synthetics/Seismic Traces
- Displaying Synthetics Well Curves
- Using the Anisotropy Tool
- Displaying the Delta Curve
- Using the Predict Window
- Configuring Volumes (Predict)
- Configuring Wells (Predict)
- Applying Filters and Including Result Curves
- Arbitrary Locations (Predict)
- Spike (Predict)
- Configuring Lithofluid Probability Tracks
- Defining View Settings (Predict)
- Legend
- PPP: Module Summary
- Operation Modes and Applications
- Pore Pressure Calculation Methods
- Module Startup and Well Settings
- Well Settings
- Well Configuration for the PPP Module
- Overburden Pressure (OBP)
- Normal Compaction Trend Lines (NCTL)
- Eaton’s Method
- Miller’s Method
- Calibration Points
- Centroid Method — Pore Pressure in a Hydraulically-Connected Formation
- 3D Model Building — Volume Preparation and 1D Well Verification
- 3D Model Building — 3D volume generation
- View Options
- Track Options
- Export Options
- PPP: Hints and Troubleshooting
- Spectra Analysis Overview
- Adding data to Spectral Analysis
- Spectral Analysis Settings
- Spectra Chart Settings
- How it Works (Spectral Analysis)
- Insight and Petrel Overview
- Installing the Petrel Link
- Linking Insight and Petrel
- Synchronise Data (Petrel Link)
- Troubleshooting: Verifying Petrel Link
- How to manually install Petrel Link?
- Insight and Kingdom Overview
- Configuring the Kingdom Link
- Using the Kingdom Link
- Downloading and Installing SQL Server 2014
- Downloading and Installing SQL Server Management Studio Express
- Manually Attaching Kingdom SQL Database
- Troubleshooting: Enabling TCP/IP in the SQL Server
- Troubleshooting: Windows services SQL Server (SMTKINGDOM) and SQL Server Browser Are Running
- Troubleshooting: File System Permissions
- Troubleshooting: Setting More Controls On The Port Used by SQL Server
- Launching the Data Manager
- Backup a Project
- Restore a Project
- Repair a Project Database
- Compact a Project Database
- Clone a Project Database
- Synchronising Projects
- Copy Objects Tool
- Command Line Control
- Reports
- About Well Manager Tool
- Using the Well Info Summary Table
- Using the Well Components Table
- Editing Labels in the Well Manager Tool
- Searching for Wells
- Formats accepted by Insight for import and export
- Insight’s Automatic Well Curve Class Assignment
- Acknowledgements
