470,619 Members | 1,600 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,619 developers. It's quick & easy.

web hoster only allows 1 sql server database

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

Jul 23 '05 #1
4 1071
You can implement 2 or more distinct schemas in one database by using
different name spaces (object owners). Using permissions, you can make each
schema invisible to other applications to prevent accidental overlap.

On 24 Apr 2005 17:39:51 -0700, "Steve Richter" <St************@gmail.com>
wrote:
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


Jul 23 '05 #2
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" <St************@gmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.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

Jul 23 '05 #3

thanks Dan and Steve. Your answers helped me a lot!

-Steve

Dan Guzman wrote:
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" <St************@gmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.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


Jul 23 '05 #4
Steve Richter wrote:
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

Why don't you just pay for their service instead of trying to circumvent it.

Jul 23 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Steve Richter | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.