Microsoft SQL Server

  • 2 minutes to read

The following *.sql script can be used to generate two tables to persist appointment and resource data.

CREATE TABLE [dbo].[Appointments] (
        [UniqueID] [int] IDENTITY (1, 1) NOT NULL ,
        [Type] [int] NULL ,
        [StartDate] [smalldatetime] NULL ,
        [EndDate] [smalldatetime] NULL ,
        [AllDay] [bit] NULL ,
        [Subject] [nvarchar] (50) NULL ,
        [Location] [nvarchar] (50) NULL ,
        [Description] [nvarchar](max) NULL ,
        [Status] [int] NULL ,
        [Label] [int] NULL ,
        [ResourceID] [int] NULL ,
        [ResourceIDs] [nvarchar](max) NULL ,
        [ReminderInfo] [nvarchar](max) NULL ,
        [RecurrenceInfo] [nvarchar](max) NULL ,
        [CustomField1] [nvarchar](max) NULL 
CONSTRAINT [PK_Appointments] PRIMARY KEY CLUSTERED
(
        [UniqueID] ASC
)
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

GO

CREATE TABLE [dbo].[Resources] (
        [UniqueID] [int] IDENTITY (1, 1) NOT NULL ,
        [ResourceID] [int] NOT NULL ,
        [ResourceName] [nvarchar] (50) NULL ,
        [Color] [int] NULL ,
        [Image] [image] NULL ,
        [CustomField1] [nvarchar](max) NULL 
CONSTRAINT [PK_Resources] PRIMARY KEY CLUSTERED
(
        [UniqueID] ASC
)
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

GO
NOTE

If SchedulerControl.ResourceSharing is enabled, map the Appointments.ResourceID property to the ResourceIDs field, which is [nvarchar](max). Otherwise, map it to the ResourceID field. The ResourceID does not necessarily need to be an integer; the Scheduler treats resource identifier as an Object type, so you can use any type supported by MS SQL Server. Make sure that the type of the ResourceID field is the same in Appointments and Resources tables.

TIP

For the complete sample project, see the following DevExpress Support Center example: http://www.devexpress.com/example=E215.

See Also