{"id":1292,"date":"2012-02-16T00:00:00","date_gmt":"2012-02-16T00:00:00","guid":{"rendered":"https:\/\/test.simple-talk.com\/uncategorized\/exploring-ssis-architecture-and-execution-history-through-scripting\/"},"modified":"2021-06-03T16:45:26","modified_gmt":"2021-06-03T16:45:26","slug":"exploring-ssis-architecture-and-execution-history-through-scripting","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/databases\/sql-server\/bi-sql-server\/exploring-ssis-architecture-and-execution-history-through-scripting\/","title":{"rendered":"Exploring SSIS Architecture and Execution History Through Scripting"},"content":{"rendered":"
\n

My previous article on SSIS<\/a> was focused on the architecture and the functioning of the product. I had also provided a few essential T-SQL scripts which provide certain ways for documenting the SSIS environment. <\/p>\n

In this article I will focus more on the T-SQL scripting and the ways to reveal configuration, performance and architectural information through scripting. <\/p>\n

Exploring SSIS’s Metadata Objects <\/h2>\n

SSIS Metadata Objects in sys.objects <\/h3>\n

Let’s start simple by exploring the metadata objects that are related to the SSIS installation. <\/p>\n

If we look at the Integration Services metadata objects in SQL 2005 we will notice that the objects contain the ‘DTS’ phrase in their names. By executing the following script in SQL 2005 we will get all objects related to the SSIS metadata (notice that the script is executed in the MSDB context): <\/p>\n

USE msdb ;\n\nSELECT  *\nFROM    sys.objects\nWHERE   name LIKE '%dts%' <\/pre>\n
Later on, in the SQL 2008 and later we have objects containing the phrase ‘DTS’ as well as ‘SSIS’ in the names. Execute the following script to view the objects (again, in the context of the MSDB database):<\/p>\n
USE msdb ;\n\nSELECT  *\nFROM    sys.objects\nWHERE   name LIKE '%dts%'\n        OR name LIKE '%ssis%' <\/pre>\n
Why is this? In SQL Server 2005 you will find dbo.sysdtspackages and dbo. sysdtspackages90, which help SQL Server distinguish between Integration Services packages created in BIDS and legacy packages inherited and transferred from the old SQL Server 2000 DTS (Data Transformation Services). <\/p>\n
In SQL Server 2008 and up we find dbo. sysdtspackages and dbo. sysssispackages, where the first table contains legacies, and the second – the BIDS packages with versions from 2005 and 2008. <\/p>\n
SSIS <\/em><\/strong>Metadata Objects in other system tables <\/h3>\n
In SQL 2008 and up we have: <\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n
name – 2008<\/strong><\/td>\n<\/tr>\n
sysdtscategories<\/td>\nOne row for each category description<\/td>\n<\/tr>\n
sysdtspackagelog<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n
sysdtspackages<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n
sysdtssteplog<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n
sysdtstasklog<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n
sysssislog<\/td>\nOne row per entry generated by SSIS package at runtime (when the SQL Server log provider is used)<\/td>\n<\/tr>\n
sysssispackagefolders<\/td>\nOne row for each folder in the SSIS structure<\/td>\n<\/tr>\n
sysssispackages<\/td>\nOne row for each SSIS package <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
… and in SQL 2005 there is … <\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n
name – 2005<\/strong><\/td>\n<\/tr>\n
sysdtscategories<\/td>\nOne row for each category description<\/td>\n<\/tr>\n
sysdtslog90<\/td>\nOne row per entry generated by SSIS package at runtime<\/td>\n<\/tr>\n
sysdtspackagefolders90<\/td>\nOne row for each folder in the SSIS structure<\/td>\n<\/tr>\n
sysdtspackagelog<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n
sysdtspackages<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n
sysdtspackages90<\/td>\nOne row for each SSIS package<\/td>\n<\/tr>\n
sysdtssteplog<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n
sysdtstasklog<\/td>\nLegacy<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Structure and contents of the SSIS packages<\/em><\/strong> <\/h2>\n
As we know, the SSIS packages are just structured XML files that contain all information needed for the package to carry out its tasks. In other words, the SSIS package itself contains the objects in the flows, the precedence, the connections and their configurations. <\/p>\n
SSIS Packages may be saved on the file system, or in MSDB repository. In the case of the package being saved in MSDB, the package definition is saved in the packagedata column of the dbo.sysssispackages table (or in dbo.sysdtspackages90 in SQL Server 2005). <\/p>\n
The column itself is of the image<\/em> datatype, hence in order for us to retrieve the contents, we need to cast it as a VARBINARY(MAX) first, and then as a XML data type. <\/p>\n
Depending on the security level of the package, however, it might not be very easy to explore the contents of the package definitions in MSDB; in case the package is encrypted, the package definition will begin with the EncryptedData<\/strong> tag. <\/p>\n
Retrieving the definitions of the SSIS Packages <\/h3>\n
So, here is how to retrieve the definitions of the SSIS packages in MSDB: <\/p>\n
In 2005: <\/strong><\/h4>\n
SELECT     p.[name] AS [PackageName]\n           ,[description] AS [PackageDescription]\n           ,CASE [packagetype]\n               WHEN 0 THEN 'Undefined'\n               WHEN 1 THEN 'SQL Server Import and Export Wizard'\n               WHEN 2 THEN 'DTS Designer in SQL Server 2000'\n               WHEN 3 THEN 'SQL Server Replication'\n               WHEN 5 THEN 'SSIS Designer'\n               WHEN 6 THEN 'Maintenance Plan Designer or Wizard'\n           END     AS [PackageType]\n           ,CASE [packageformat]\n               WHEN 0 THEN 'SSIS 2005 version'\n               WHEN 1 THEN 'SSIS 2008 version'\n           END AS [PackageFormat]\n           ,p.[createdate]\n           ,CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML) PackageXML\n          FROM      [msdb].[dbo].[sysdtspackages90]     p <\/pre>\n
In 2008 and up: <\/h4>\n
SELECT     p.[name] AS [PackageName]\n           ,[description] AS [PackageDescription]\n           ,CASE [packagetype]\n               WHEN 0 THEN 'Undefined'\n               WHEN 1 THEN 'SQL Server Import and Export Wizard'\n               WHEN 2 THEN 'DTS Designer in SQL Server 2000'\n               WHEN 3 THEN 'SQL Server Replication'\n               WHEN 5 THEN 'SSIS Designer'\n               WHEN 6 THEN 'Maintenance Plan Designer or Wizard'\n           END     AS [PackageType]\n           ,CASE [packageformat]\n               WHEN 0 THEN 'SSIS 2005 version'\n               WHEN 1 THEN 'SSIS 2008 version'\n           END AS [PackageFormat]\n           ,p.[createdate]\n           ,CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML) PackageXML\n          FROM      [msdb].[dbo].[sysssispackages]     p <\/pre>\n
Now that we have the definition, what can we do with it? We can parse it and extract some useful data. <\/p>\n
Extracting connection strings from an SSIS definition <\/h3>\n
Here is how to retrieve the data connection strings: <\/p>\n
In SQL 2005: <\/h4>\n
;WITH XMLNAMESPACES ('www.microsoft.com\/SqlServer\/Dts' AS pNS1,\n  'www.microsoft.com\/SqlServer\/Dts' AS DTS) -- declare XML namespaces\nSELECT c.name,\n  SSIS_XML.value('.\/pNS1:Property [@pNS1:Name=\"DelayValidation\"][1]', \n    'varchar(100)') AS DelayValidation,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ObjectName\"][1]', \n    'varchar(100)') AS ObjectName,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"Description\"][1]', \n    'varchar(100)') AS Description,\n   SSIS_XML.value('pNS1:ObjectData[1]\/pNS1:ConnectionManager[1]\n\/pNS1:Property[@pNS1:Name=\"Retain\"][1]', 'varchar(MAX)') Retain,  \n   SSIS_XML.value('pNS1:ObjectData[1]\/pNS1:ConnectionManager[1]\n\/pNS1:Property[@pNS1:Name=\"ConnectionString\"][1]', 'varchar(MAX)') ConnectionString\nFROM  \n--\n( SELECT    id ,\n                    CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML) PackageXML\n          FROM      [msdb].[dbo].[sysdtspackages90]\n        ) PackageXML\n        CROSS APPLY PackageXML.nodes('\/DTS:Executable\/DTS:ConnectionManager') SSIS_XML ( SSIS_XML )\n        INNER JOIN [msdb].[dbo].[sysdtspackages90] c ON PackageXML.id = c.id <\/pre>\n
In SQL 2008 and up: <\/h4>\n
;WITH XMLNAMESPACES ('www.microsoft.com\/SqlServer\/Dts' AS pNS1,\n  'www.microsoft.com\/SqlServer\/Dts' AS DTS) -- declare XML namespaces\nSELECT c.name,\n  SSIS_XML.value('.\/pNS1:Property [@pNS1:Name=\"DelayValidation\"][1]', \n    'varchar(100)') AS DelayValidation,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ObjectName\"][1]', \n    'varchar(100)') AS ObjectName,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"Description\"][1]', \n    'varchar(100)') AS Description,\n   SSIS_XML.value('pNS1:ObjectData[1]\/pNS1:ConnectionManager[1]\n\/pNS1:Property[@pNS1:Name=\"Retain\"][1]', 'varchar(MAX)') Retain,  \n   SSIS_XML.value('pNS1:ObjectData[1]\/pNS1:ConnectionManager[1]\n\/pNS1:Property[@pNS1:Name=\"ConnectionString\"][1]', 'varchar(MAX)') ConnectionString\nFROM  \n--\n( SELECT    id ,\n                    CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML) PackageXML\n          FROM      [msdb].[dbo].[sysssispackages]\n        ) PackageXML\n        CROSS APPLY PackageXML.nodes('\/DTS:Executable\/DTS:ConnectionManager') SSIS_XML ( SSIS_XML )\n        INNER JOIN [msdb].[dbo].[sysssispackages] c ON PackageXML.id = c.id <\/pre>\n
Extracting connection strings from an SSIS definition <\/h3>\n
Here is how to retrieve the package configurations: <\/p>\n
In SQL 2005: <\/h4>\n
;WITH XMLNAMESPACES ('www.microsoft.com\/SqlServer\/Dts' AS pNS1,\n  'www.microsoft.com\/SqlServer\/Dts' AS DTS) -- declare XML namespaces\nSELECT c.name,\n  SSIS_XML.value('.\/pNS1:Property [@pNS1:Name=\"ConfigurationType\"][1]', \n    'varchar(100)') AS ConfigurationType,\n  CASE CAST(SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ConfigurationType\"][1]', \n    'varchar(100)') AS INT)\n    WHEN 0 THEN 'Parent Package'\n    WHEN 1 THEN 'XML File'\n    WHEN 2 THEN 'Environmental Variable'\n    WHEN 3 THEN 'Registry Entry'\n    WHEN 4 THEN 'Parent Package via Environmental Variable'\n    WHEN 5 THEN 'XML File via Environmental Variable'\n    WHEN 6 THEN 'Registry Entry via Environmental Variable'\n    WHEN 7 THEN 'SQL Server'\n  END AS ConfigurationTypeDesc,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ConfigurationVariable\"][1]', \n    'varchar(100)') AS ConfigurationVariable,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ObjectName\"][1]', \n    'varchar(100)') AS ConfigurationName,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ConfigurationString\"][1]', \n    'varchar(100)') AS ConfigurationString\nFROM  \n( SELECT    id ,\n                    CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML) PackageXML\n          FROM      [msdb].[dbo].[sysdtspackages90]\n        ) PackageXML\n        CROSS APPLY PackageXML.nodes('\/DTS:Executable\/DTS:Configuration') SSIS_XML ( SSIS_XML )\n        INNER JOIN [msdb].[dbo].[sysdtspackages90] c ON PackageXML.id = c.id <\/pre>\n
In SQL 2008 and up: <\/h4>\n
;WITH XMLNAMESPACES ('www.microsoft.com\/SqlServer\/Dts' AS pNS1,\n  'www.microsoft.com\/SqlServer\/Dts' AS DTS) -- declare XML namespaces\nSELECT c.name,\n  SSIS_XML.value('.\/pNS1:Property [@pNS1:Name=\"ConfigurationType\"][1]', \n    'varchar(100)') AS ConfigurationType,\n  CASE CAST(SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ConfigurationType\"][1]', \n    'varchar(100)') AS INT)\n    WHEN 0 THEN 'Parent Package'\n    WHEN 1 THEN 'XML File'\n    WHEN 2 THEN 'Environmental Variable'\n    WHEN 3 THEN 'Registry Entry'\n    WHEN 4 THEN 'Parent Package via Environmental Variable'\n    WHEN 5 THEN 'XML File via Environmental Variable'\n    WHEN 6 THEN 'Registry Entry via Environmental Variable'\n    WHEN 7 THEN 'SQL Server'\n  END AS ConfigurationTypeDesc,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ConfigurationVariable\"][1]', \n    'varchar(100)') AS ConfigurationVariable,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ObjectName\"][1]', \n    'varchar(100)') AS ConfigurationName,\n  SSIS_XML.value('.\/pNS1:Property[@pNS1:Name=\"ConfigurationString\"][1]', \n    'varchar(100)') AS ConfigurationString\nFROM  \n( SELECT    id ,\n                    CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML) PackageXML\n          FROM      [msdb].[dbo].[sysssispackages]\n        ) PackageXML\n        CROSS APPLY PackageXML.nodes('\/DTS:Executable\/DTS:Configuration') SSIS_XML ( SSIS_XML )\n        INNER JOIN [msdb].[dbo].[sysssispackages] c ON PackageXML.id = c.id <\/pre>\n
There are many other aspects to be explored in the definitions of the SSIS packages, and it is all matter of finding the node names and parsing them. <\/p>\n
In the remaining part of this article, I would like to shift our attention to these areas: the interaction between SQL Agent and the SSIS packages and some scripts to gather performance statistics. <\/p>\n
Overriding the package internal configurations<\/em><\/strong> <\/h2>\n
The SSIS packages can be executed in several ways: as a scheduled job from the SQL Server Agent or from the command line (or even from a batch file). <\/p>\n
Regardless of which method is used for the execution, it is always the DTExec.exe who carries the task. <\/p>\n
Before executing the SSIS package, the SQL Server Agent or the command line script have to form an execution string and pass parameters to the DTExec, and thus control the execution of the package. <\/p>\n
Here is a script which shows all SQL Agent jobs steps which execute SSIS packages and the custom configurations provided through the SQL Agent job: <\/p>\n
USE [msdb]\nGO\nSELECT j.job_id,\n       s.srvname,\n       j.name,\n       js.subsystem,\n       js.step_id,\n       js.command,\n       j.enabled,\n       js.output_file_name,\n       js.last_run_outcome,\n       js.last_run_duration,\n       js.last_run_retries,\n       js.last_run_date,\n       js.last_run_time,\n        js.proxy_id \nFROM   dbo.sysjobs j\nJOIN   dbo.sysjobsteps js\n   ON  js.job_id = j.job_id \nJOIN   MASTER.dbo.sysservers s\n   ON  s.srvid = j.originating_server_id\n--filter only the job steps which are executing SSIS packages \nWHERE  subsystem = 'SSIS'\n--use the line below to enter some search criteria\n--AND js.command LIKE N'%ENTER_SEARCH%'\nGO <\/pre>\n
As you noticed, you can even use the script above to filter and search through the configurations of the SQL Agent Jobs. For example, you can search for all jobs which are executing encrypted SSIS packages by using … <\/p>\n
AND    js.command LIKE N'%\/DECRYPT%' <\/pre>\n
…as a search criteria in the above script. You may also want to search for a server name, for example. <\/p>\n
Exploring <\/em><\/strong>execution history<\/em><\/strong> <\/h2>\n
Finally, let’s look into some execution history of the SSIS packages which are scheduled as SQL Server Agent jobs. <\/p>\n
The following script will return all SQL Server Agent Jobs, which are currently (as of the moment of the execution of the script) executing SSIS packages and also the last execution time and duration, as well as the execution command. <\/p>\n
SET NOCOUNT ON\n-- Check if the SQL Server Agent is running\nIF EXISTS ( SELECT  1\n            FROM    MASTER.dbo.sysprocesses\n            WHERE   program_name = N'SQLAgent - Generic Refresher' ) \n    BEGIN\n        SELECT  @@SERVERNAME AS 'InstanceName' ,\n                1 AS 'SQLServerAgentRunning'\n    END\nELSE \n    BEGIN\n        SELECT  @@SERVERNAME AS 'InstanceName' ,\n                0 AS 'SQLServerAgentRunning'               \n        RAISERROR('The SQL Server Agent is not running.', 16, 1) WITH SETERROR ;               \n    END\n-- Execute the script\nIF EXISTS ( SELECT  *\n            FROM    tempdb.dbo.sysobjects\n            WHERE   id = OBJECT_ID(N'[tempdb].[dbo].[Temp1]') ) \n    DROP TABLE [tempdb].[dbo].[Temp1]\nGO\nCREATE TABLE [tempdb].[dbo].[Temp1]\n    (\n      job_id UNIQUEIDENTIFIER NOT NULL ,\n      last_run_date NVARCHAR(20) NOT NULL ,\n      last_run_time NVARCHAR(20) NOT NULL ,\n      next_run_date NVARCHAR(20) NOT NULL ,\n      next_run_time NVARCHAR(20) NOT NULL ,\n      next_run_schedule_id INT NOT NULL ,\n      requested_to_run INT NOT NULL ,\n      request_source INT NOT NULL ,\n      request_source_id SYSNAME COLLATE database_default\n                                NULL ,\n      running INT NOT NULL ,\n      current_step INT NOT NULL ,\n      current_retry_attempt INT NOT NULL ,\n      job_state INT NOT NULL\n    )\nDECLARE @job_owner SYSNAME\nDECLARE @is_sysadmin INT\nSET @is_sysadmin = ISNULL(IS_SRVROLEMEMBER('sysadmin'), 0)\nSET @job_owner = SUSER_SNAME()\nINSERT  INTO [tempdb].[dbo].[Temp1]\n        EXECUTE MASTER.dbo.xp_sqlagent_enum_jobs @is_sysadmin, @job_owner\n        \nUPDATE  [tempdb].[dbo].[Temp1]\nSET     last_run_time = RIGHT('000000' + last_run_time, 6) ,\n        next_run_time = RIGHT('000000' + next_run_time, 6) ;\n-----\nSELECT  j.name AS JobName ,\n        j.enabled AS Enabled ,\n        CASE x.running\n          WHEN 1 THEN 'Running'\n          ELSE CASE h.run_status\n                 WHEN 2 THEN 'Inactive'\n                 WHEN 4 THEN 'Inactive'\n                 ELSE 'Completed'\n               END\n        END AS CurrentStatus ,\n        COALESCE(x.current_step, 0) AS CurrentStepNbr ,\n        CASE x.running\n          WHEN 1 THEN js.step_name\n          ELSE NULL\n        END AS CurrentStepName ,\n        CASE WHEN x.last_run_date > 0\n             THEN CONVERT (DATETIME, SUBSTRING(x.last_run_date, 1, 4) + '-'\n                  + SUBSTRING(x.last_run_date, 5, 2) + '-'\n                  + SUBSTRING(x.last_run_date, 7, 2) + ' '\n                  + SUBSTRING(x.last_run_time, 1, 2) + ':'\n                  + SUBSTRING(x.last_run_time, 3, 2) + ':'\n                  + SUBSTRING(x.last_run_time, 5, 2) + '.000', 121)\n             ELSE NULL\n        END AS LastRunTime ,\n        CASE h.run_status\n          WHEN 0 THEN 'Fail'\n          WHEN 1 THEN 'Success'\n          WHEN 2 THEN 'Retry'\n          WHEN 3 THEN 'Cancel'\n          WHEN 4 THEN 'In progress'\n        END AS LastRunOutcome ,\n        CASE WHEN h.run_duration > 0\n             THEN ( h.run_duration \/ 1000000 ) * ( 3600 * 24 )\n                  + ( h.run_duration \/ 10000 % 100 ) * 3600 + ( h.run_duration\n                                                              \/ 100 % 100 )\n                  * 60 + ( h.run_duration % 100 )\n             ELSE NULL\n        END AS LastRunDuration ,\n        js.command AS SSISPackageExecutionCommand\nFROM    [tempdb].[dbo].[Temp1] x\n        LEFT JOIN msdb.dbo.sysjobs j ON x.job_id = j.job_id\n        JOIN msdb.dbo.sysjobsteps js ON js.job_id = j.job_id\n        LEFT OUTER JOIN msdb.dbo.syscategories c ON j.category_id = c.category_id\n        LEFT OUTER JOIN msdb.dbo.sysjobhistory h ON x.job_id = h.job_id\n                                                    AND x.last_run_date = h.run_date\n                                                    AND x.last_run_time = h.run_time\n                                                    AND h.step_id = 0\nWHERE   x.running = 1\n        AND js.subsystem = 'SSIS'\n\nDROP TABLE [tempdb].[dbo].[Temp1] <\/pre>\n
In conclusion, SSIS is a vast product which provides significant amount of metadata available to the SQL Server administrator. In this article I have shown the way to explore the SSIS metadata through some scripts and hopefully they will make the daily administration of your SSIS environments much easier. <\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
When you are using SSIS, there soon comes a time when you are confronted with having to do a tricky task such as searching for particular connection strings in all your SSIS packages, or checking the execution history of scheduled SSIS jobs.  You can do this type of work effectively in TSQL as Feodor explains.…<\/p>\n","protected":false},"author":221902,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[143528],"tags":[5424,4296,5606,4150,4306,5605,4190],"coauthors":[],"class_list":["post-1292","post","type-post","status-publish","format-standard","hentry","category-bi-sql-server","tag-integration-services","tag-metadata","tag-scripting","tag-sql","tag-ssis","tag-ssis-architecture","tag-tsql"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1292","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/221902"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=1292"}],"version-history":[{"count":4,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1292\/revisions"}],"predecessor-version":[{"id":40643,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1292\/revisions\/40643"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=1292"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=1292"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=1292"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=1292"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}