![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
What can be done if the shared web hoster I am using allows only 1 sql server database and a second web application I would like to install is configured to use its own database? can databases be nested, one within another? thanks, -Steve |
#3
| |||
| |||
|
|
What can be done if the shared web hoster I am using allows only 1 sql server database and a second web application I would like to install is configured to use its own database? can databases be nested, one within another? thanks, -Steve |
#4
| |||
| |||
|
|
The separate schema approach suggested by Steve is a good one but a caveat is that you'll need different logins in order to implement that solution. If your provider limits you to a single login, you can still deploy as many apps as you like in a single database using the 'dbo' schema as long as you have no object name conflicts. You can adopt an object naming convention to make it easier to identify the associated application. -- Hope this helps. Dan Guzman SQL Server MVP "Steve Richter" <StephenRichter (AT) gmail (DOT) com> wrote in message news:1114389591.250302.312760 (AT) z14g2000cwz (DOT) googlegroups.com... What can be done if the shared web hoster I am using allows only 1 sql server database and a second web application I would like to install is configured to use its own database? can databases be nested, one within another? thanks, -Steve |
#5
| |||
| |||
|
|
What can be done if the shared web hoster I am using allows only 1 sql server database and a second web application I would like to install is configured to use its own database? can databases be nested, one within another? thanks, -Steve |
![]() |
| Thread Tools | |
| Display Modes | |
| |