We've got a SQL-2005-Database in the back of an asp.net-Application. We are using the SQLMembershipProvider to manage the Users.
Now the problem is, that the aspnet_users-table with only about 500 Users uses 88MB space (I guess it's primarily index-space) - which I find is a lot. The customer has a very expensive database-hosting-provider, so every MB counts.
My first question: is it normal that so little user-records produce such a large amount of index-data? Second: how can I reduce the space needed?
I have to admit that I'm not really a proficient sql-server-user. Usually I create the database and tables without much additional optimization.