Greetings,

I'm trying to come to terms with the membership database created
automatically in ASP.NET applications that use membership functionality. My
problem is that I need to implement more information than is stored in the
default membership database.

For example, I would like to efficiently get the number of users in a
particular role. From what I've told, the most efficient way is by writing a
stored procedure. But, for a number of reasons, it seems like it would make
sense to leave the membership database alone and put my custom stuff in a
seprate database. So this leaves the question of how I'd approach writing
such a stored procedure that worked with data in another database. As far as
I know, that is not possible.

Any suggestions?

Thanks.

prompt user to select from recordset.
Large VB ADO.NET Recordset Import into Excel
Reading a SQLCLR Stored Proc. Result
Better way for dropdownlists
Add Records