Companies, Shopping Carts, etc... where is the standard place to put the
tables? I want to link it to the user/membership tables. BUT, is it "ok" or
the standard practice to go ahead and use the ASPNETDB.mdf to store your own
tables?For small web sites the solution you've specified is fine.
Larger web sites will likely have their own database, in which case the
membership table either remain in a separate database or the SQL scripts are
run to include the tables in the site's main database.
--
I hope this helps,
Steve C. Orr
MCSD, MVP
http://Steve.Orr.net
"VB Programmer" wrote:
> If you want to store custom tables in ASP.NET 2.0, such as Products,
> Companies, Shopping Carts, etc... where is the standard place to put the
> tables? I want to link it to the user/membership tables. BUT, is it "ok" or
> the standard practice to go ahead and use the ASPNETDB.mdf to store your own
> tables?
>
>
Excellent response!
Now, if I deploy a ASPNETDB.mdf with custom tables, etc..., if I LATER add a
table, or field, etc... what is the best way to update the database without
losting current data? Is Enterprise Manager the tool I can use? If so,
what password do I use to get into the ASPNETDB.mdf? I tried with 'sa' (no
password) with no success.
(I have MSDN Universal account so might have access to other tools you
recommend.)
Thanks!
Robert
"Steve C. Orr" <Steve@.Orr.net> wrote in message
news:2AC76A85-C1B3-40C9-8056-4294C6101277@.microsoft.com...
> For small web sites the solution you've specified is fine.
> Larger web sites will likely have their own database, in which case the
> membership table either remain in a separate database or the SQL scripts
> are
> run to include the tables in the site's main database.
> --
> I hope this helps,
> Steve C. Orr
> MCSD, MVP
> http://Steve.Orr.net
>
> "VB Programmer" wrote:
>> If you want to store custom tables in ASP.NET 2.0, such as Products,
>> Companies, Shopping Carts, etc... where is the standard place to put the
>> tables? I want to link it to the user/membership tables. BUT, is it "ok"
>> or
>> the standard practice to go ahead and use the ASPNETDB.mdf to store your
>> own
>> tables?
>>
>>
>>
>
Check this out:
http://www.microsoft.com/downloads/...&displaylang=en
--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"VB Programmer" <dont@.emailme.com> wrote in message
news:eAeUe5%23FGHA.644@.TK2MSFTNGP09.phx.gbl...
> Excellent response!
> Now, if I deploy a ASPNETDB.mdf with custom tables, etc..., if I LATER add
> a table, or field, etc... what is the best way to update the database
> without losting current data? Is Enterprise Manager the tool I can use?
> If so, what password do I use to get into the ASPNETDB.mdf? I tried with
> 'sa' (no password) with no success.
> (I have MSDN Universal account so might have access to other tools you
> recommend.)
> Thanks!
> Robert
> "Steve C. Orr" <Steve@.Orr.net> wrote in message
> news:2AC76A85-C1B3-40C9-8056-4294C6101277@.microsoft.com...
>> For small web sites the solution you've specified is fine.
>> Larger web sites will likely have their own database, in which case the
>> membership table either remain in a separate database or the SQL scripts
>> are
>> run to include the tables in the site's main database.
>>
>> --
>> I hope this helps,
>> Steve C. Orr
>> MCSD, MVP
>> http://Steve.Orr.net
>>
>>
>>
>> "VB Programmer" wrote:
>>
>>> If you want to store custom tables in ASP.NET 2.0, such as Products,
>>> Companies, Shopping Carts, etc... where is the standard place to put the
>>> tables? I want to link it to the user/membership tables. BUT, is it
>>> "ok" or
>>> the standard practice to go ahead and use the ASPNETDB.mdf to store your
>>> own
>>> tables?
>>>
>>>
>>>
>>>
Thanks once again Steve!
"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
news:OLgX3pAGGHA.3064@.TK2MSFTNGP10.phx.gbl...
> Check this out:
> http://www.microsoft.com/downloads/...&displaylang=en
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://SteveOrr.net
>
> "VB Programmer" <dont@.emailme.com> wrote in message
> news:eAeUe5%23FGHA.644@.TK2MSFTNGP09.phx.gbl...
>> Excellent response!
>>
>> Now, if I deploy a ASPNETDB.mdf with custom tables, etc..., if I LATER
>> add a table, or field, etc... what is the best way to update the
>> database without losting current data? Is Enterprise Manager the tool I
>> can use? If so, what password do I use to get into the ASPNETDB.mdf? I
>> tried with 'sa' (no password) with no success.
>>
>> (I have MSDN Universal account so might have access to other tools you
>> recommend.)
>>
>> Thanks!
>> Robert
>>
>> "Steve C. Orr" <Steve@.Orr.net> wrote in message
>> news:2AC76A85-C1B3-40C9-8056-4294C6101277@.microsoft.com...
>>> For small web sites the solution you've specified is fine.
>>> Larger web sites will likely have their own database, in which case the
>>> membership table either remain in a separate database or the SQL scripts
>>> are
>>> run to include the tables in the site's main database.
>>>
>>> --
>>> I hope this helps,
>>> Steve C. Orr
>>> MCSD, MVP
>>> http://Steve.Orr.net
>>>
>>>
>>>
>>> "VB Programmer" wrote:
>>>
>>>> If you want to store custom tables in ASP.NET 2.0, such as Products,
>>>> Companies, Shopping Carts, etc... where is the standard place to put
>>>> the
>>>> tables? I want to link it to the user/membership tables. BUT, is it
>>>> "ok" or
>>>> the standard practice to go ahead and use the ASPNETDB.mdf to store
>>>> your own
>>>> tables?
>>>>
>>>>
>>>>
>>>>
>>
>>
I don't know which username was selected by default. I never remember
selecting one and have already uploaded the ASPNETDB.MDF to the site here:
http://www.MySite.com/App_data/aspnetdb.mdf
How would I connect to it?
Thanks.
"VB Programmer" <dont@.emailme.com> wrote in message
news:eD1NHWEGGHA.1032@.TK2MSFTNGP11.phx.gbl...
> Thanks once again Steve!
> "Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
> news:OLgX3pAGGHA.3064@.TK2MSFTNGP10.phx.gbl...
>> Check this out:
>> http://www.microsoft.com/downloads/...&displaylang=en
>>
>> --
>> I hope this helps,
>> Steve C. Orr, MCSD, MVP
>> http://SteveOrr.net
>>
>>
>> "VB Programmer" <dont@.emailme.com> wrote in message
>> news:eAeUe5%23FGHA.644@.TK2MSFTNGP09.phx.gbl...
>>> Excellent response!
>>>
>>> Now, if I deploy a ASPNETDB.mdf with custom tables, etc..., if I LATER
>>> add a table, or field, etc... what is the best way to update the
>>> database without losting current data? Is Enterprise Manager the tool I
>>> can use? If so, what password do I use to get into the ASPNETDB.mdf? I
>>> tried with 'sa' (no password) with no success.
>>>
>>> (I have MSDN Universal account so might have access to other tools you
>>> recommend.)
>>>
>>> Thanks!
>>> Robert
>>>
>>> "Steve C. Orr" <Steve@.Orr.net> wrote in message
>>> news:2AC76A85-C1B3-40C9-8056-4294C6101277@.microsoft.com...
>>>> For small web sites the solution you've specified is fine.
>>>> Larger web sites will likely have their own database, in which case the
>>>> membership table either remain in a separate database or the SQL
>>>> scripts are
>>>> run to include the tables in the site's main database.
>>>>
>>>> --
>>>> I hope this helps,
>>>> Steve C. Orr
>>>> MCSD, MVP
>>>> http://Steve.Orr.net
>>>>
>>>>
>>>>
>>>> "VB Programmer" wrote:
>>>>
>>>>> If you want to store custom tables in ASP.NET 2.0, such as Products,
>>>>> Companies, Shopping Carts, etc... where is the standard place to put
>>>>> the
>>>>> tables? I want to link it to the user/membership tables. BUT, is it
>>>>> "ok" or
>>>>> the standard practice to go ahead and use the ASPNETDB.mdf to store
>>>>> your own
>>>>> tables?
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>>
0 comments:
Post a Comment