hi,

 Can any help to solve this, i had surf'd the net could find any proper answer. We are on the way to implement Web parts. have a large number of register'd user.

For Personalization of Webparts which is the best method App_Data\ASPNETDB.mdf or SQL SERVER 2005

How many user will be supported if i implement Personalization  using App_Data\ASPNETDB.mdf , is it using SQL SERVER Express Edition host?

and what about the problem with user instance if i implement Personalization  using  SQL SERVER 2005.

Thanks in advance.

Kcube

I think its better to used ASPNETDB as your Database because it is designed for webparts and personalization.. I would also suggest to removed the ASPNETDB file under your AppData Folder and transfer it in your Sql Server DB for you to Extend it.. Just map it in your web config file for you to connect the database in your apps by setting the connection strings... 

hi,

Thanks for the reply,

if i implement the webparts personalization in ASPNETDB.mdf file under your AppData Folder ,

1. how many users will it support, if its implemented under  AppData Folder  ?

2. Is there any restriction in the data size of aspnetdb.mdf, if its implemented under  AppData Folder  ?

3. Will my web site get slowdown if the size of aspnetdb.mdf is large (if its implemented under  AppData Folder ) ?

 Hi, I'm not really sure about all this, but this is at least what I would think 

 >>1. how many users will it support, if its implemented under  AppData Folder
>> 2. Is there any restriction in the data size of aspnetdb.mdf, if its implemented under  AppData Folder  ?
When you are using a datafile in your AppData folder, you are only using the SQL(Express) engine to work with. The actually data is stored in the file on your web site and as far as I know there is no limitation on the size of the file.  But with most webhost providers, there is a limitation on web space. So... you can store as much data in it as your web space allows you to. Don't forget that you are then sharing it also with your web files.

 >> 3. Will my web site get slowdown if the size of aspnetdb.mdf is large (if its implemented under  AppData Folder ) ?
This can be... after all, it must read the file from another location. I presume you will notice it if you have very large records and you need to search through it. Don't know how indexing works when using a database file.

I would prefer using a database if you have the chance than a file in the app_data folder.  Express server allows only 4GB of max database size, which is still a lot for a small company (depending what you need to save).

hi,

Thanks James Dean for the reply.

can any one point out the relevant links about this topic.

Best Regards

KCube

How can we map it with our custom database in sql server 2005 if we dont want to use aspnetdb?

falaky :

How can we map it with our custom database in sql server 2005 if we dont want to use aspnetdb?

You need to create your Own Custom Personalization Provider to handle the personalization of WebParts

http://msdn.microsoft.com/en-us/library/aa479037.aspx 

thanks

 The example in the link http://msdn.microsoft.com/en-us/library/aa479037.aspx talks about how to use a different datasource other than sql server.

 What if I want to use a different schema (I have an existing database with the member information)? 

indyanguy:

 The example in the link http://msdn.microsoft.com/en-us/library/aa479037.aspx talks about how to use a different datasource other than sql server.

 What if I want to use a different schema (I have an existing database with the member information)? 

• You wish to store personalization data in a data source that is not supported by the Web Parts personalization providers included with the .NET Framework, such as an Oracle database.
• You wish to store personalization data in a SQL Server database WHOSE SCHEMA DIFFERS from that of the database used by System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.

Please try to go back to the link and read it once again for your reference..

Thanks 

 Yes, I do understand that I can write a custom provider for a different schema. I am unable to find an example of what methods should be overriden and how to get started.

 Our application has a table that stores a LoginId (a unique ID) and I understand that the ASPNETDB uses  GUID to track Users for personalization. If we only want to include WebParts and don't care about Membership for now, do we need all the tables in the ASPNETDB? Can I include only the ones for personalization in our existing app?

 Any advice is really appreciated.

 any help is really appreciated