My Application is to Store Various Notification details with type and some other fields Using SQL Server 2008 database.
I am going to make one table and mange all data in single table and display records and there titles using case statement for now. But i am little bit worried about managing data in large scale with complex call to display data or muliltiple people doing operation in single table at same time when it will be live.
Which will makes sense to manage records in one large table or Different tables.
Web Site and Database managing with shared server with ram amount of 1 GB.
Speed considerations in calling, updating or searching/manipulating?
Here's example of my Single table structure:
Notification : NotificationId, NotificationType, Title, Description, NotificationDate, UserId, IP, RepeatEveryDay, RepeatTill, etc.
Here's example of some of Multiple table structure:
ReminderNotification : ReminderNotificationId, ReminderTitle, ReminderDescription, NotificationDate, RepeatEveryDay, RepeatTill, UserId, IP, etc.
SportsNotification : SportsNotificationId, SportsTitle, SportsDescription, NotificationDate, UserId, IP, etc.
NewsNotification : NewsNotificationId, NewsTitle, NewsDescription, NotificationDate, UserId, IP, etc.
FashionNotification : FashionNotificationId, FashionTitle, FashionDescription, NotificationDate, UserId, IP, etc.
5 More tables Like Last one.
What I have tried:
SQL Query execution time comparing with Single & Mutliple table. But both executed in almost same amount of time.