Saturday, May 3, 2008

create custom database for Membership,role,profile in sql server

if u want to use custom database on the sqlserver insteade of database in App_Data folder

u use following instruction
to create membership and role ,profile in ur database
C:WINDOWSMicrosoft.NETFrameworkv2.0.50727>aspnet_regsql.exe -E -S sureshserver -d Useraccount -A mr

Start adding the following features:
Membership
RoleManager

..................

Finished.

for help

C:WINDOWSMicrosoft.NETFrameworkv2.0.50727>aspnet_regsql.exe /?

Administrative utility to install and uninstall ASP.NET features on a SQL
server.
Copyright (C) Microsoft Corporation. All rights reserved.

 

                             -- GENERAL OPTIONS --

-?                Display this help text.

-W                Wizard mode. (Default if no other parameters are specified.)
                          -- SQL CONNECTION OPTIONS --

-S <server>       SQL Server instance (SQL Server 7.0 and above) to work with.

-U <login id>     SQL Server user name to authenticate with; requires -P
                  option.

-P <password>     SQL Server password to authenticate with; requires -U option.

-E                Authenticate with current Windows credentials.

-C <connection string>
                  Connection string. Instead of specifying a user name,
                  password, and server name, specify a SQL Server connection
                  string. The string must not contain a database name unless
                  otherwise specified.

-sqlexportonly <filename>
                  Generate the SQL script file for adding or removing the
                  specified features and do not carry out the actual operation.
                  Can be used with the following options: -A, -R, -ssadd, and
                  -ssremove.
                       -- APPLICATION SERVICES OPTIONS --

-A all|m|r|p|c|w  Add support for a feature. Multiple values can be specified
                  together. For example:

                      -A mp
                      -A m -A p

                  all: All features
                  m: Membership
                  r: Role manager
                  p: Profiles
                  c: Personalization
                  w: SQL Web event provider

-R all|m|r|p|c|w  Remove support for a feature. Multiple values can be
                  specified together. For example:

                      -R mp
                      -R m -R p

                  all : All features plus all common tables and stored
                  procedures shared by the features
                  m: Membership
                  r: Role manager
                  p: Profiles
                  c: Personalization
                  w: SQL Web event provider

-d <database>     Database name for use with application services. If no
                  database name is specified, the default database "aspnetdb"
                  is used.

-Q                Quiet mode; do not display confirmation to remove a feature.

 

           -- SQL CACHE DEPENDENCY OPTIONS (FOR SQL 7.0 AND 2000) --

-d <database>     Database name for use with SQL cache dependency in SQL 7.0
                  and SQL 2000. The database can optionally be specified using
                  the connection string with the -C option instead. (Required)

-ed               Enable a database for SQL cache dependency.

-dd               Disable a database for SQL cache dependency.

-et               Enable a table for SQL cache dependency. Requires -t option.

-dt               Disable a table for SQL cache dependency. Requires -t option.

-t <table>        Name of the table to enable or disable for SQL cache
                  dependency. Requires -et or -dt option.

-lt               List all tables enabled for SQL cache dependency.
                          -- SESSION STATE OPTIONS --

-ssadd            Add support for SQLServer mode session state.

-ssremove         Remove support for SQLServer mode session state.

-sstype t|p|c     Type of session state support:

                  t: temporary. Session state data is stored in the "tempdb"
                  database. Stored procedures for managing session are
                  installed in the "ASPState" database. Data is not persisted
                  if you restart SQL. (Default)

                  p: persisted. Both session state data and the stored
                  procedures are stored in the "ASPState" database.

                  c: custom. Both session state data and the stored procedures
                  are stored in a custom database. The database name must be
                  specified.

-d <database>     The name of the custom database to use if -sstype is "c".

C:WINDOWSMicrosoft.NETFrameworkv2.0.50727>

1 comment :

  1. Hi,

    I want to know if you can customise the membership schema to add more fields to the existing tables and also add more tables to the schema. We have a requirement where apart from the usual username/password type login we have 2 other types of login users. One of them uses Certificates and another is authenticated by another application which then passes back an identifier to our app for the logged on user. I would like to add more fields to the existing schema tables and also add more tables. How easy is to change the available functionality which comes with the membership schema to be changed...like the stored procs, the middle layer methods etc.

    Any help would be much appreciated.

    Thanks
    Arvinder

    ReplyDelete

AJAX, asp, Asp.net, asp.net and sql server security, Asp.net IntemIndex, C#, Css, DataBinder.Eval, DataKeyNames, Datalist, Datapager, DataSet, DataTable, DropDownList, FindControl, gridview, JavaScript, jquery, Listview, Paging, Regex, RegularExpression, Repeater, Server side validation, Sql Server, timer, timercallback, Validation, XML, xmlnode, XPath