# Analiza przed migracją

## 🔍 Inwentaryzacja baz danych
Lista baz danych do migracji:
- **cerberus_eu** (Serwer: BISSEORSQLCLU01, Rozmiar: 31426.88 MB, Poziom zgodności: CompatLevel120)
- **cerberus_stats** (Serwer: BISSEORSQLCLU01, Rozmiar: 167432.50 MB, Poziom zgodności: CompatLevel120)
- **DBadminOp** (Serwer: BISSEORSQLCLU01, Rozmiar: 1274.00 MB, Poziom zgodności: CompatLevel120)
- **test** (Serwer: BISSEORSQLCLU01, Rozmiar: 7.25 MB, Poziom zgodności: CompatLevel120)
- **trade** (Serwer: BISSEORSQLCLU01, Rozmiar: 165644.56 MB, Poziom zgodności: CompatLevel110)
- **AdressdirektExternal** (Serwer: WPSQL01\WPSQL01, Rozmiar: 147433.94 MB, Poziom zgodności: CompatLevel120)
- **clr_util** (Serwer: WPSQL01\WPSQL01, Rozmiar: 6.50 MB, Poziom zgodności: CompatLevel120)
- **comhem** (Serwer: WPSQL01\WPSQL01, Rozmiar: 10537.44 MB, Poziom zgodności: CompatLevel120)
- **infoadress** (Serwer: WPSQL01\WPSQL01, Rozmiar: 25274.31 MB, Poziom zgodności: CompatLevel120)
- **Infoadress_worklkd** (Serwer: WPSQL01\WPSQL01, Rozmiar: 41620.00 MB, Poziom zgodności: CompatLevel120)
- **infoadressplats** (Serwer: WPSQL01\WPSQL01, Rozmiar: 205969.25 MB, Poziom zgodności: CompatLevel120)
- **infoadressplats_work** (Serwer: WPSQL01\WPSQL01, Rozmiar: 106671.50 MB, Poziom zgodności: CompatLevel120)
- **infoadressplatsgis** (Serwer: WPSQL01\WPSQL01, Rozmiar: 4643.00 MB, Poziom zgodności: CompatLevel120)
- **infoadressplatsgis_external** (Serwer: WPSQL01\WPSQL01, Rozmiar: 47777.94 MB, Poziom zgodności: CompatLevel120)
- **infobatch** (Serwer: WPSQL01\WPSQL01, Rozmiar: 46757.44 MB, Poziom zgodności: CompatLevel120)
- **Infobest** (Serwer: WPSQL01\WPSQL01, Rozmiar: 1039.62 MB, Poziom zgodności: CompatLevel120)
- **infobest_urval** (Serwer: WPSQL01\WPSQL01, Rozmiar: 2345.06 MB, Poziom zgodności: CompatLevel120)
- **rawdata** (Serwer: WPSQL01\WPSQL01, Rozmiar: 39230.06 MB, Poziom zgodności: CompatLevel120)
- **tele** (Serwer: WPSQL01\WPSQL01, Rozmiar: 62384.94 MB, Poziom zgodności: CompatLevel120)
- **tele2** (Serwer: WPSQL01\WPSQL01, Rozmiar: 12070.62 MB, Poziom zgodności: CompatLevel120)
- **teleavis** (Serwer: WPSQL01\WPSQL01, Rozmiar: 5341.00 MB, Poziom zgodności: CompatLevel120)
- **teleboniro** (Serwer: WPSQL01\WPSQL01, Rozmiar: 37252.88 MB, Poziom zgodności: CompatLevel120)
- **teleinfo_external** (Serwer: WPSQL01\WPSQL01, Rozmiar: 182932.38 MB, Poziom zgodności: CompatLevel120)
- **teleonlinews** (Serwer: WPSQL01\WPSQL01, Rozmiar: 23722.12 MB, Poziom zgodności: CompatLevel120)
- **Track_Avisering** (Serwer: WPSQL01\WPSQL01, Rozmiar: 21867.50 MB, Poziom zgodności: CompatLevel120)

## 🛠️ Problemy zgodności
Lista obiektów wymagających uwagi:
### Baza danych: DBadminOp
  - Procedure `dbo.NCM_helpdb`: Remove references to undocumented system tables — Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 73, Column 45.
 Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 122, Column 45.
  - Procedure `dbo.NCM_helpdb`: Remove references to undocumented system tables — Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 73, Column 45.
 Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 122, Column 45.
  - Procedure `dbo.NCM_helpdb`: Remove references to undocumented system tables — Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 73, Column 45.
 Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 122, Column 45.
  - Procedure `dbo.NCM_helpdb`: Remove references to undocumented system tables — Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 73, Column 45.
 Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 122, Column 45.
  - Procedure `dbo.NCM_helpdb`: Remove references to undocumented system tables — Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 73, Column 45.
 Table spt_values has changed or does not longer exist after SQL Server 2005. Using it may cause errors. For more details, please see: Line 122, Column 45.
  - Procedure `dbo.ncm_instance_info`: Unqualified Join(s) detected — Object [dbo].[ncm_instance_info] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 129, Column 1.
  - Procedure `dbo.ncm_instance_info`: Unqualified Join(s) detected — Object [dbo].[ncm_instance_info] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 129, Column 1.
  - Procedure `dbo.ncm_instance_info`: Unqualified Join(s) detected — Object [dbo].[ncm_instance_info] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 129, Column 1.
  - Procedure `dbo.ncm_instance_info`: Unqualified Join(s) detected — Object [dbo].[ncm_instance_info] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 129, Column 1.
  - Procedure `dbo.ncm_instance_info`: Unqualified Join(s) detected — Object [dbo].[ncm_instance_info] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 129, Column 1.
### Baza danych: AdressdirektExternal
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_BA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 44, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 43, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunFTG_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunFTG_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_CNRAddress`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 47, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 73, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_BA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunFTGAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunFTGAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_CNRAvis`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_CNRAvis] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 29, Column 4.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_BA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 44, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 43, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunFTG_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunFTG_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_CNRAddress`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 47, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 73, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_BA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunFTGAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunFTGAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_CNRAvis`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_CNRAvis] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 29, Column 4.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_BA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 44, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 43, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunFTG_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunFTG_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_CNRAddress`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 47, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 73, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_BA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunFTGAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunFTGAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_CNRAvis`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_CNRAvis] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 29, Column 4.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_BA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 44, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 43, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunFTG_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunFTG_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_CNRAddress`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 47, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 73, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_BA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunFTGAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunFTGAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_CNRAvis`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_CNRAvis] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 29, Column 4.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_BA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 44, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunArbetsstalle_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunArbetsstalle_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 43, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_BasunFTG_PA`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_BasunFTG_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 3.
  - Procedure `dbo.UpdateRenormed_IAPLID_CNRAddress`: Unqualified Join(s) detected — Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 47, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 3.
 Object [dbo].[UpdateRenormed_IAPLID_CNRAddress] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 73, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_BA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_BA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_BasunArbetsstalleAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunArbetsstalleAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 3.
  - Procedure `dbo.Update_IAPLID_BasunFTGAvis_PA`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_BasunFTGAvis_PA] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 26, Column 4.
  - Procedure `dbo.Update_IAPLID_CNRAvis`: Unqualified Join(s) detected — Object [dbo].[Update_IAPLID_CNRAvis] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 29, Column 4.
### Baza danych: clr_util
  - Assembly `Adress`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[Adress]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `Core (AdressCLR\RegEx2\Core)`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[Core (AdressCLR\RegEx2\Core)]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `GIS`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[GIS]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `MightyLittleGeodesy`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[MightyLittleGeodesy]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `NormCore`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[NormCore]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `NormProxy`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[NormProxy]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `RegEx`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[RegEx]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `Adress`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[Adress]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `Core (AdressCLR\RegEx2\Core)`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[Core (AdressCLR\RegEx2\Core)]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `GIS`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[GIS]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `MightyLittleGeodesy`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[MightyLittleGeodesy]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `NormCore`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[NormCore]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `NormProxy`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[NormProxy]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `RegEx`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[RegEx]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `Adress`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[Adress]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `Core (AdressCLR\RegEx2\Core)`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[Core (AdressCLR\RegEx2\Core)]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `GIS`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[GIS]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `MightyLittleGeodesy`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[MightyLittleGeodesy]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `NormCore`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[NormCore]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `NormProxy`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[NormProxy]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `RegEx`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[RegEx]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
### Baza danych: infoadressplatsgis
  - Column `dbo.BricGeometryGIS.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.BricGeometryGIS.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 9, Column 5.
  - Column `dbo.BricGeometryGIS.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.BricGeometryGIS.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 9, Column 5.
  - Column `dbo.BricGeometryGIS.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.BricGeometryGIS.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 9, Column 5.
  - Column `dbo.BricGeometryGIS.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.BricGeometryGIS.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 9, Column 5.
  - Column `dbo.BricGeometryGIS.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.BricGeometryGIS.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 9, Column 5.
### Baza danych: infoadressplatsgis_external
  - Procedure `dbo.Zoom_PrepareSwedStreetPart1`: Unqualified Join(s) detected — Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 279, Column 3.
 Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 336, Column 3.
  - Procedure `dbo.Zoom_PrepareSwedStreetPart1`: Unqualified Join(s) detected — Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 279, Column 3.
 Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 336, Column 3.
  - Procedure `dbo.Zoom_PrepareSwedStreetPart1`: Unqualified Join(s) detected — Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 279, Column 3.
 Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 336, Column 3.
  - Procedure `dbo.Zoom_PrepareSwedStreetPart1`: Unqualified Join(s) detected — Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 279, Column 3.
 Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 336, Column 3.
  - Procedure `dbo.Zoom_PrepareSwedStreetPart1`: Unqualified Join(s) detected — Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 279, Column 3.
 Object [dbo].[Zoom_PrepareSwedStreetPart1] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 336, Column 3.
  - Column `dbo.SwedStreetGSD.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.SwedStreetGSD.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 11, Column 5.
  - Column `dbo.SwedStreetGSD.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.SwedStreetGSD.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 11, Column 5.
  - Column `dbo.SwedStreetGSD.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.SwedStreetGSD.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 11, Column 5.
  - Column `dbo.SwedStreetGSD.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.SwedStreetGSD.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 11, Column 5.
  - Column `dbo.SwedStreetGSD.SW_GEOMETRY`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.SwedStreetGSD.SW_GEOMETRY uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 11, Column 5.
### Baza danych: infobatch
  - Assembly `InfodataBatchSQLCLRIntegration`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[InfodataBatchSQLCLRIntegration]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `InfodataBatchSQLCLRIntegration`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[InfodataBatchSQLCLRIntegration]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Assembly `InfodataBatchSQLCLRIntegration`: CLR assemblies marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE — Assembly '[InfodataBatchSQLCLRIntegration]' with PERMISSION_SET = 'Safe' cannot be migrated. For more details, please see: Line 1, Column 1.
  - Procedure `dbo.FetchQueueInformation`: Unqualified Join(s) detected — Object [dbo].[FetchQueueInformation] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 40, Column 1.
  - Procedure `dbo.FetchUnfinishedBatches`: Unqualified Join(s) detected — Object [dbo].[FetchUnfinishedBatches] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 5, Column 47.
  - Procedure `dbo.FetchQueueInformation`: Unqualified Join(s) detected — Object [dbo].[FetchQueueInformation] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 40, Column 1.
  - Procedure `dbo.FetchUnfinishedBatches`: Unqualified Join(s) detected — Object [dbo].[FetchUnfinishedBatches] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 5, Column 47.
  - Procedure `dbo.FetchQueueInformation`: Unqualified Join(s) detected — Object [dbo].[FetchQueueInformation] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 40, Column 1.
  - Procedure `dbo.FetchUnfinishedBatches`: Unqualified Join(s) detected — Object [dbo].[FetchUnfinishedBatches] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 5, Column 47.
  - Procedure `dbo.FetchQueueInformation`: Unqualified Join(s) detected — Object [dbo].[FetchQueueInformation] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 40, Column 1.
  - Procedure `dbo.FetchUnfinishedBatches`: Unqualified Join(s) detected — Object [dbo].[FetchUnfinishedBatches] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 5, Column 47.
  - Procedure `dbo.FetchQueueInformation`: Unqualified Join(s) detected — Object [dbo].[FetchQueueInformation] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 40, Column 1.
  - Procedure `dbo.FetchUnfinishedBatches`: Unqualified Join(s) detected — Object [dbo].[FetchUnfinishedBatches] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 5, Column 47.
  - Procedure `dbo.fetchAllBatchServers`: ORDER BY specifies integer ordinal — Object [dbo].[fetchAllBatchServers] uses ORDER BY clause specifiying ordinal column numbers as sort columns, this is not supported in database compatibility level 90 and higher. For more details, please see: Line 22, Column 30.
  - Procedure `dbo.fetchAllBatchServers`: ORDER BY specifies integer ordinal — Object [dbo].[fetchAllBatchServers] uses ORDER BY clause specifiying ordinal column numbers as sort columns, this is not supported in database compatibility level 90 and higher. For more details, please see: Line 22, Column 30.
  - Procedure `dbo.fetchAllBatchServers`: ORDER BY specifies integer ordinal — Object [dbo].[fetchAllBatchServers] uses ORDER BY clause specifiying ordinal column numbers as sort columns, this is not supported in database compatibility level 90 and higher. For more details, please see: Line 22, Column 30.
  - Procedure `dbo.fetchAllBatchServers`: ORDER BY specifies integer ordinal — Object [dbo].[fetchAllBatchServers] uses ORDER BY clause specifiying ordinal column numbers as sort columns, this is not supported in database compatibility level 90 and higher. For more details, please see: Line 22, Column 30.
  - Procedure `dbo.fetchAllBatchServers`: ORDER BY specifies integer ordinal — Object [dbo].[fetchAllBatchServers] uses ORDER BY clause specifiying ordinal column numbers as sort columns, this is not supported in database compatibility level 90 and higher. For more details, please see: Line 22, Column 30.
  - Column `dbo.ErrorAndEventLog.FormattedMessage`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorAndEventLog.FormattedMessage uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 8, Column 5.
  - Column `dbo.ErrorAndEventLog.FormattedMessage`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorAndEventLog.FormattedMessage uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 8, Column 5.
  - Column `dbo.ErrorAndEventLog.FormattedMessage`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorAndEventLog.FormattedMessage uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 8, Column 5.
  - Column `dbo.ErrorAndEventLog.FormattedMessage`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorAndEventLog.FormattedMessage uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 8, Column 5.
  - Column `dbo.ErrorAndEventLog.FormattedMessage`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorAndEventLog.FormattedMessage uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 8, Column 5.
### Baza danych: Infobest
  - Procedure `dbo.SSIS_CreateOrderForNotifications`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.
  - Procedure `dbo.SSIS_CreateOrderForNotifications`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.
  - Procedure `dbo.SSIS_CreateOrderForNotifications`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.
  - Procedure `dbo.SSIS_CreateOrderForNotifications`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.
### Baza danych: infobest_urval
  - Column `dbo.dtproperties.lvalue`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.dtproperties.lvalue uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 7, Column 5.
  - Column `dbo.dtproperties.lvalue`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.dtproperties.lvalue uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 7, Column 5.
  - Column `dbo.dtproperties.lvalue`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.dtproperties.lvalue uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 7, Column 5.
  - Column `dbo.dtproperties.lvalue`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.dtproperties.lvalue uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 7, Column 5.
  - Column `dbo.dtproperties.lvalue`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.dtproperties.lvalue uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 7, Column 5.
### Baza danych: rawdata
  - Procedure `dbo.KL_Fixa_Skellefteå_TurTestOmrade`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 53, Column 112.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 61, Column 52.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 64, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 54, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 59, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL_Arsta`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 55, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 60, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 63, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 66, Column 69.
  - Procedure `dbo.KL_Fixa_Skellefteå_TurTestOmrade`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 53, Column 112.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 61, Column 52.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 64, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 54, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 59, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL_Arsta`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 55, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 60, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 63, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 66, Column 69.
  - Procedure `dbo.KL_Fixa_Skellefteå_TurTestOmrade`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 53, Column 112.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 61, Column 52.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 64, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 54, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 59, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL_Arsta`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 55, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 60, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 63, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 66, Column 69.
  - Procedure `dbo.KL_Fixa_Skellefteå_TurTestOmrade`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 53, Column 112.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 61, Column 52.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 64, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 54, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 59, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL_Arsta`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 55, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 60, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 63, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 66, Column 69.
  - Procedure `dbo.KL_Fixa_Skellefteå_TurTestOmrade`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 53, Column 112.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 61, Column 52.
 Object [dbo].[KL_Fixa_Skellefteå_TurTestOmrade] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 64, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 54, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 59, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 65, Column 69.
  - Procedure `dbo.KL_Fixa_TURURVAL_Arsta`: Unqualified Join(s) detected — Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 55, Column 112.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 60, Column 95.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 63, Column 52.
 Object [dbo].[KL_Fixa_TURURVAL_Arsta] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 66, Column 69.
### Baza danych: tele
  - Procedure `dbo.PoliceParameterSearch`: Unqualified Join(s) detected — Object [dbo].[PoliceParameterSearch] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 150, Column 3.
  - Procedure `dbo.PoliceParameterSearch`: Unqualified Join(s) detected — Object [dbo].[PoliceParameterSearch] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 150, Column 3.
  - Procedure `dbo.PoliceParameterSearch`: Unqualified Join(s) detected — Object [dbo].[PoliceParameterSearch] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 150, Column 3.
  - Procedure `dbo.PoliceParameterSearch`: Unqualified Join(s) detected — Object [dbo].[PoliceParameterSearch] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 150, Column 3.
  - Procedure `dbo.PoliceParameterSearch`: Unqualified Join(s) detected — Object [dbo].[PoliceParameterSearch] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 150, Column 3.
### Baza danych: tele2
  - Procedure `dbo.Insert_AppartmentNo_Temp`: Unqualified Join(s) detected — Object [dbo].[Insert_AppartmentNo_Temp] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 78, Column 44.
  - Procedure `dbo.Insert_AppartmentNo_Temp`: Unqualified Join(s) detected — Object [dbo].[Insert_AppartmentNo_Temp] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 78, Column 44.
  - Procedure `dbo.Insert_AppartmentNo_Temp`: Unqualified Join(s) detected — Object [dbo].[Insert_AppartmentNo_Temp] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 78, Column 44.
  - Procedure `dbo.Insert_AppartmentNo_Temp`: Unqualified Join(s) detected — Object [dbo].[Insert_AppartmentNo_Temp] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 78, Column 44.
  - Procedure `dbo.Insert_AppartmentNo_Temp`: Unqualified Join(s) detected — Object [dbo].[Insert_AppartmentNo_Temp] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 78, Column 44.
### Baza danych: teleavis
  - Column `dbo.ErrorRowsInDataFile.PersonNo`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorRowsInDataFile.PersonNo uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 2, Column 5.
  - Column `dbo.ErrorRowsInDataFile.PersonNo`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorRowsInDataFile.PersonNo uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 2, Column 5.
  - Column `dbo.ErrorRowsInDataFile.PersonNo`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorRowsInDataFile.PersonNo uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 2, Column 5.
  - Column `dbo.ErrorRowsInDataFile.PersonNo`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorRowsInDataFile.PersonNo uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 2, Column 5.
  - Column `dbo.ErrorRowsInDataFile.PersonNo`: Deprecated data types TEXT, IMAGE or NTEXT — Object dbo.ErrorRowsInDataFile.PersonNo uses deprecated data type TEXT, IMAGE or NTEXT which will be discontinued for future versions of SQL Server. For more details, please see: Line 2, Column 5.
### Baza danych: teleboniro
  - Procedure `dbo.DTS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[DTS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 105, Column 3.
  - Procedure `dbo.SSIS_Fill_Candidate`: Unqualified Join(s) detected — Object [dbo].[SSIS_Fill_Candidate] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 92, Column 5.
  - Procedure `dbo.SSIS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 106, Column 3.
  - Procedure `dbo.SSIS_Update_Boniro_Phone`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Phone] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 403, Column 3.
  - Procedure `dbo.xSys_CreateCodeGeneratorColumns`: Unqualified Join(s) detected — Object [dbo].[xSys_CreateCodeGeneratorColumns] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 89, Column 1.
  - ScalarFunction `dbo.xSys_GetdataType`: Unqualified Join(s) detected — Object [dbo].[xSys_GetdataType] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 38, Column 1.
  - ScalarFunction `dbo.xSys_GetNullSubstitute`: Unqualified Join(s) detected — Object [dbo].[xSys_GetNullSubstitute] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 1.
  - Procedure `dbo.DTS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[DTS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 105, Column 3.
  - Procedure `dbo.SSIS_Fill_Candidate`: Unqualified Join(s) detected — Object [dbo].[SSIS_Fill_Candidate] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 92, Column 5.
  - Procedure `dbo.SSIS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 106, Column 3.
  - Procedure `dbo.SSIS_Update_Boniro_Phone`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Phone] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 403, Column 3.
  - Procedure `dbo.xSys_CreateCodeGeneratorColumns`: Unqualified Join(s) detected — Object [dbo].[xSys_CreateCodeGeneratorColumns] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 89, Column 1.
  - ScalarFunction `dbo.xSys_GetdataType`: Unqualified Join(s) detected — Object [dbo].[xSys_GetdataType] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 38, Column 1.
  - ScalarFunction `dbo.xSys_GetNullSubstitute`: Unqualified Join(s) detected — Object [dbo].[xSys_GetNullSubstitute] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 1.
  - Procedure `dbo.DTS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[DTS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 105, Column 3.
  - Procedure `dbo.SSIS_Fill_Candidate`: Unqualified Join(s) detected — Object [dbo].[SSIS_Fill_Candidate] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 92, Column 5.
  - Procedure `dbo.SSIS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 106, Column 3.
  - Procedure `dbo.SSIS_Update_Boniro_Phone`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Phone] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 403, Column 3.
  - Procedure `dbo.xSys_CreateCodeGeneratorColumns`: Unqualified Join(s) detected — Object [dbo].[xSys_CreateCodeGeneratorColumns] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 89, Column 1.
  - ScalarFunction `dbo.xSys_GetdataType`: Unqualified Join(s) detected — Object [dbo].[xSys_GetdataType] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 38, Column 1.
  - ScalarFunction `dbo.xSys_GetNullSubstitute`: Unqualified Join(s) detected — Object [dbo].[xSys_GetNullSubstitute] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 1.
  - Procedure `dbo.DTS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[DTS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 105, Column 3.
  - Procedure `dbo.SSIS_Fill_Candidate`: Unqualified Join(s) detected — Object [dbo].[SSIS_Fill_Candidate] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 92, Column 5.
  - Procedure `dbo.SSIS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 106, Column 3.
  - Procedure `dbo.SSIS_Update_Boniro_Phone`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Phone] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 403, Column 3.
  - Procedure `dbo.xSys_CreateCodeGeneratorColumns`: Unqualified Join(s) detected — Object [dbo].[xSys_CreateCodeGeneratorColumns] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 89, Column 1.
  - ScalarFunction `dbo.xSys_GetdataType`: Unqualified Join(s) detected — Object [dbo].[xSys_GetdataType] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 38, Column 1.
  - ScalarFunction `dbo.xSys_GetNullSubstitute`: Unqualified Join(s) detected — Object [dbo].[xSys_GetNullSubstitute] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 1.
  - Procedure `dbo.DTS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[DTS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 105, Column 3.
  - Procedure `dbo.SSIS_Fill_Candidate`: Unqualified Join(s) detected — Object [dbo].[SSIS_Fill_Candidate] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 92, Column 5.
  - Procedure `dbo.SSIS_Update_Boniro_Person`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Person] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 106, Column 3.
  - Procedure `dbo.SSIS_Update_Boniro_Phone`: Unqualified Join(s) detected — Object [dbo].[SSIS_Update_Boniro_Phone] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 403, Column 3.
  - Procedure `dbo.xSys_CreateCodeGeneratorColumns`: Unqualified Join(s) detected — Object [dbo].[xSys_CreateCodeGeneratorColumns] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 89, Column 1.
  - ScalarFunction `dbo.xSys_GetdataType`: Unqualified Join(s) detected — Object [dbo].[xSys_GetdataType] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 38, Column 1.
  - ScalarFunction `dbo.xSys_GetNullSubstitute`: Unqualified Join(s) detected — Object [dbo].[xSys_GetNullSubstitute] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 42, Column 1.
  - ScalarFunction `dbo.xSys_GetPrimaryKeyColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetPrimaryKeyColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 32, Column 10.
  - ScalarFunction `dbo.xSys_GetTableColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetTableColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 39, Column 10.
  - ScalarFunction `dbo.xSys_GetPrimaryKeyColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetPrimaryKeyColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 32, Column 10.
  - ScalarFunction `dbo.xSys_GetTableColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetTableColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 39, Column 10.
  - ScalarFunction `dbo.xSys_GetPrimaryKeyColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetPrimaryKeyColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 32, Column 10.
  - ScalarFunction `dbo.xSys_GetTableColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetTableColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 39, Column 10.
  - ScalarFunction `dbo.xSys_GetPrimaryKeyColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetPrimaryKeyColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 32, Column 10.
  - ScalarFunction `dbo.xSys_GetTableColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetTableColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 39, Column 10.
  - ScalarFunction `dbo.xSys_GetPrimaryKeyColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetPrimaryKeyColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 32, Column 10.
  - ScalarFunction `dbo.xSys_GetTableColumnsXML`: FOR XML AUTO queries return derived table references in 90 or later compatibility modes — Object [dbo].[xSys_GetTableColumnsXML] runs a FOR XML query that executes in AUTO mode, which returns references to derived table aliases. Under compatibility level 90 or later, the query returns references to the derived table alias instead of to the derived table's base tables, so you should modify your application as required to account for the changes. For more details, please see: Line 39, Column 10.
### Baza danych: teleinfo_external
  - Procedure `dbo.GetTeleInfoNotificationStatistics`: Syntax issue on the source server — Object [dbo].[GetTeleInfoNotificationStatistics] has syntax errors. Incorrect syntax near compute.. Error number 46010. For more details, please see: Line 27, Column 1.
  - Procedure `dbo.GetTeleInfoNotificationStatistics`: Syntax issue on the source server — Object [dbo].[GetTeleInfoNotificationStatistics] has syntax errors. Incorrect syntax near compute.. Error number 46010. For more details, please see: Line 27, Column 1.
  - Procedure `dbo.GetTeleInfoNotificationStatistics`: Syntax issue on the source server — Object [dbo].[GetTeleInfoNotificationStatistics] has syntax errors. Incorrect syntax near compute.. Error number 46010. For more details, please see: Line 27, Column 1.
  - Procedure `dbo.GetTeleInfoNotificationStatistics`: Syntax issue on the source server — Object [dbo].[GetTeleInfoNotificationStatistics] has syntax errors. Incorrect syntax near compute.. Error number 46010. For more details, please see: Line 27, Column 1.
  - Procedure `dbo.GetTeleInfoNotificationStatistics`: Syntax issue on the source server — Object [dbo].[GetTeleInfoNotificationStatistics] has syntax errors. Incorrect syntax near compute.. Error number 46010. For more details, please see: Line 27, Column 1.
  - Procedure `dbo.SSIS_FOR_AVIS`: Unqualified Join(s) detected — Object [dbo].[SSIS_FOR_AVIS] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 218, Column 3.
  - Procedure `dbo.SSIS_UpdateReNormedAddresses`: Unqualified Join(s) detected — Object [dbo].[SSIS_UpdateReNormedAddresses] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 77.
  - Procedure `dbo.SSIS_FOR_AVIS`: Unqualified Join(s) detected — Object [dbo].[SSIS_FOR_AVIS] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 218, Column 3.
  - Procedure `dbo.SSIS_UpdateReNormedAddresses`: Unqualified Join(s) detected — Object [dbo].[SSIS_UpdateReNormedAddresses] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 77.
  - Procedure `dbo.SSIS_FOR_AVIS`: Unqualified Join(s) detected — Object [dbo].[SSIS_FOR_AVIS] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 218, Column 3.
  - Procedure `dbo.SSIS_UpdateReNormedAddresses`: Unqualified Join(s) detected — Object [dbo].[SSIS_UpdateReNormedAddresses] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 77.
  - Procedure `dbo.SSIS_FOR_AVIS`: Unqualified Join(s) detected — Object [dbo].[SSIS_FOR_AVIS] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 218, Column 3.
  - Procedure `dbo.SSIS_UpdateReNormedAddresses`: Unqualified Join(s) detected — Object [dbo].[SSIS_UpdateReNormedAddresses] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 77.
  - Procedure `dbo.SSIS_FOR_AVIS`: Unqualified Join(s) detected — Object [dbo].[SSIS_FOR_AVIS] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 218, Column 3.
  - Procedure `dbo.SSIS_UpdateReNormedAddresses`: Unqualified Join(s) detected — Object [dbo].[SSIS_UpdateReNormedAddresses] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher. For more details, please see: Line 62, Column 77.
  - Procedure `dbo.SSIS_CreateOrderForNotifications2`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications2] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.
  - Procedure `dbo.SSIS_CreateOrderForNotifications2`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications2] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.
  - Procedure `dbo.SSIS_CreateOrderForNotifications2`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications2] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.
  - Procedure `dbo.SSIS_CreateOrderForNotifications2`: SET ROWCOUNT used in the context of DML statements such as INSERT, UPDATE, or DELETE — Object [dbo].[SSIS_CreateOrderForNotifications2] uses SET ROWCOUNT in conjunction with an INSERT, UPDATE or DELETE statement. For more details, please see: Line 1, Column 1.

## 📋 Ocena środowiska docelowego
- Docelowa platforma: **SqlServerWindows2022**
- Wersje SQL Server: 12.0.6449.1
- Architektura: on-premises
- Wymagania wydajnościowe i pojemnościowe: do określenia na podstawie obciążenia i SLA
- Wymagania bezpieczeństwa: szyfrowanie, audyt, zgodność z politykami organizacji