asked on

view interpretation

Hi,

An unofficial dba extracted some view definitions for us but doesn't know a lot about them. Part of the text file he delivered were sections that look like the one below.
Can anyone shed some light on what this is for? If I'm just interested in the actual SQL portion can I ignore it?

SQL Server 2012 environment.

Thanks!

--Ben

EXEC sys.sp_addextendedproperty @name=N'MS_DiagramPane1', @value=N'[0E232FF0-B466-11cf-A24F-00AA00A3EFFF, 1.00]
Begin DesignProperties =
   Begin PaneConfigurations =
      Begin PaneConfiguration = 0
         NumPanes = 4
         Configuration = "(H (1[40] 4[20] 2[20] 3) )"
      End
      Begin PaneConfiguration = 1
         NumPanes = 3
         Configuration = "(H (1 [50] 4 [25] 3))"
      End
      Begin PaneConfiguration = 2
         NumPanes = 3
         Configuration = "(H (1 [50] 2 [25] 3))"
      End
      Begin PaneConfiguration = 3
         NumPanes = 3
         Configuration = "(H (4 [30] 2 [40] 3))"
      End
      Begin PaneConfiguration = 4
         NumPanes = 2
         Configuration = "(H (1 [56] 3))"
      End
      Begin PaneConfiguration = 5
         NumPanes = 2
         Configuration = "(H (2 [66] 3))"
      End
      Begin PaneConfiguration = 6
         NumPanes = 2
         Configuration = "(H (4 [50] 3))"
      End
      Begin PaneConfiguration = 7
         NumPanes = 1
         Configuration = "(V (3))"
      End
      Begin PaneConfiguration = 8
         NumPanes = 3
         Configuration = "(H (1[56] 4[18] 2) )"
      End
      Begin PaneConfiguration = 9
         NumPanes = 2
         Configuration = "(H (1 [75] 4))"
      End
      Begin PaneConfiguration = 10
         NumPanes = 2
         Configuration = "(H (1[66] 2) )"
      End
      Begin PaneConfiguration = 11
         NumPanes = 2
         Configuration = "(H (4 [60] 2))"
      End
      Begin PaneConfiguration = 12
         NumPanes = 1
         Configuration = "(H (1) )"
      End
      Begin PaneConfiguration = 13
         NumPanes = 1
         Configuration = "(V (4))"
      End
      Begin PaneConfiguration = 14
         NumPanes = 1
         Configuration = "(V (2))"
      End
      ActivePaneConfig = 0
   End
   Begin DiagramPane =
      Begin Origin =
         Top = 0
         Left = 0
      End
      Begin Tables =
         Begin Table = "RecipientManagedCareEligibility"
            Begin Extent =
               Top = 6
              Left = 38
               Bottom = 221
               Right = 299
            End
            DisplayFlags = 280
            TopColumn = 5
         End
      End
   End
   Begin SQLPane =
   End
   Begin DataPane =
      Begin ParameterDefaults = ""
      End
      Begin ColumnWidths = 9
         Width = 284
         Width = 1500
         Width = 1500
         Width = 1500
         Width = 1500
         Width = 1500
         Width = 1500
         Width = 1500
         Width = 1500
      End
   End
   Begin CriteriaPane =
      Begin ColumnWidths = 11
         Column = 1440
         Alias = 900
         Table = 1170
         Output = 720
         Append = 1400
         NewValue = 1170
         SortType = 1350
         SortOrder = 1410
         GroupBy = 1350
         Filter = 1350
         Or = 1350
         Or = 1350
         Or = 1350
      End
   End
End
' , @level0type=N'SCHEMA',@level0name=N'dbo', @level1type=N'VIEW',@level1name=N'v_ProvID'
GO

Open in new window

ASKER CERTIFIED SOLUTION

Pawan Kumar

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Ben Conner

ASKER

Ah. Thank you! I had no idea what it was. Am not the dba on this server. In fact they won't even install SSMS on my workstation. Sigh.

Much appreciated!

--Ben

Mark Wills

@Ben Conner,

It is not as a result of the query designer to create the view. In fact, it is not part of the view and can be ignored / removed.

It is Extended Properties added to Database Diagram and was included in the generate script task. Probably selecting 'Entire Database' when generating scripts.

The line : EXEC sys.sp_addextendedproperty @name=N'MS_DiagramPane1', is the giveaway as to origins.

You can exclude Extended properties when generating scripts, or, better still, drop the unwanted/ unimportant extended properties so it doesnt re-appear.

To drop the extended property - check first though because extended properties can apply to different objects - and if it isnt needed/wanted - https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-dropextendedproperty-transact-sql

To avoid future incursions, if you use the Generate Scripts task, go into options and disable 'scripting of extended properties' - there are a LOT of options in there - and only script the objects you actually need and want.

Hope that properly clarifies for you.

Ben Conner

ASKER

Thanks, Mark. This project has been a bit frustrating as the management there won't give me SSMS access so I have to guess or try stuff at home where I have the appropriate toys installed.

--Ben

Mark Wills

Yep, that would be very frustrating.

And as frustrating as it is, dont worry, because we will always be here for you.

Cheers,
Mark Wills