For your clustered index, consider an artificial key - an Integer Identity column. Because you can schedule rooms in the future, they won't be inserted in order by date.

I have to agree with Eirikur on the design. The larger issue is that it doesn't support scenarios that are likely to come up. For example:

1. What if one event needs smoke machine 1, tables and chairs?

2. Do you have a finite number of chairs you can allocate at any one time?

3. I trust you have a finite number of rooms and that the room capacity would be a property of the room, not the event.

4. Please tell me this Excel screen is just a copy of the data pasted into a worksheet. Dates should be stored as dates.

5. Do the event times have a corresponding start time and end time that'll never change? I'd think actual start and end datetime columns would be a better approach if you want to rent rooms for flexible time periods.

There's a lot of duplicated data here. You should probably consider normalizing your structure.

Hope this helps.