Microsoft Office Tutorials and References
In Depth Information
Of course, you’ll need to know the name of the existing database and the SQL Server instance on
which it’s located.
When the web application is created, you do not want to create a new site collection to complete the
install; after all, the content database already has the site collections and enclosed sites. Instead,
just reset IIS by running this:
iisreset /noforce
Then go to your new web application URL, where you’ll see the old sites from the content database.
If, on the odd occasion it doesn’t work, you can run the attach database command in STSADM or
PowerShell. This will force SharePoint to realize the content database should be accessible from
the web application.
The Bottom Line
Create and customize a new site collection. A new site collection has separate
permissions, its own Recycle Bins, its own storage quota, and its own site collection galleries. You
can change the regional settings and grant someone site administrator rights on a new site
collection without compromising your existing sites.
Master It You created a new site collection with a storage quota of 100 MB. Since then, it
has hit capacity, and no one can add new documents or list items. You asked quite a few
users to delete data to free up space, but it didn’t appear to help. Short of increasing the
quota, what can you do?
Create a new web application. A new web application is fundamentally a new IIS Web Site
with a new content database on the back end. Using a new IIS Web Site allows you to change
the port for accessing the web application, use a host header, and adjust the IIS-level
authentication such as anonymous access. Web applications, in addition to being a security boundary,
are also a boundary for settings such as RSS, sending alerts, upload size limits, and blocked
file types that affect all contained site collections. All SharePoint site collections must reside
in a web application. At this level, serious changes can affect the way the site collections are
accessed and controlled.
Master It You want to create a new web application but don’t want to use a custom port,
so you set up a host header instead. But although it appears to have been created correctly
and you created a site collection, you cannot seem to access the site. What is the most
likely problem?
Use managed paths. SharePoint uses managed paths to tell IIS which paths in a URL are
handled by SharePoint and are, therefore, managed . All other paths are considered excluded ,
and IIS is free to use them with traditional websites. You can add your own managed paths,
adjusting the URL of site collections.
By default, SharePoint site collections have two managed paths: the path (root), which is
explicit, and the path /sites/, which is a wildcard path.
Master It You create a new wildcard managed path at http://myserver/sales but
cannot seem to place a site collection in this URL without adding another piece to the
path. What is wrong?
Search JabSto ::

Custom Search