Good info on "Ghosting"

Discussion on how opening/editing a WSS or SPS2003 site in FrontPage
2003 un-ghosts the site (places the site’s definition into the SQL
database instead of keeping the reference to the one on the server).
This can be very bad for performance!


Usage Analysis Tools in SharePoint Products and Technologies

Good TechNet article on how SharePoint uses access logs (it is
actually a chapter from the Microsoft SharePoint Products and
Technologies Resource Kit which you can find here:

Why information is kept about users deleted from site collections

You can tell if the users have been deleted from the site collection
by looking at the UserInfo table of the content database. If the value
of the tp_Deleted column is 0, then the user is active in the site
collection. Otherwise, they have been removed.

SharePoint keeps this information around because it needs it to link
to the items placed on the sites. If it removed the users completely,
the items would become orphaned.

Creating New Documents from library menu

The article is a little hard to understand, but it has some pretty
good information about creating additional buttons in libraries so you
can say “New Excel file” or “New Word file” no matter the default
document library’s new file type:

In pursuit of the least amount of SQL privileges

There are some who want to find the least amount of privileges for
SharePoint to have in SQL. So, to help out, here is what I have so

The account the SharePoint Application Pool is using needs to have
read/write privileges on the content database. It also needs to have
execute privileges on stored procedures.

Host Headers, IIS, SharePoint, & SSL

Some info on how IIS works with host headers and SSL:
You shouldn’t have two sites setup with the same host header (even if
they are on different servers, UNLESS you are using load-balancing!).
A suggestion might be to call it ,, as you go through devlopment, testing, and production

Also, you have to understand how IIS works. It receives a request for
“” and looks to see if there is a virtual server listening
on port 80 (because no port was defined in the request) that is
listening for (using a host header). If it doesn’t find
one, it looks for a site listening on port 80 with no host header
defined. If it can’t find one, then it will return a bad host name

So, you need to make sure you have one, and only one, IIS virtual
server with the host header value of the site, listening on port 80
(you can use a different port, but you will of course need to use port notation), not assigned to an IP address. If you
have been playing around with the configuration, it might be that the
site is “stopped”. Click on the virtual server and refresh the screen
to see if it truely is running.

Also note, host header values do NOT come into play when dealing with
SSL. You can only have one SSL site running on port 443 per server/IP
address. But since you shouldn’t use IP address assigning, you can
only have one SSL protected SharePoint site per server using port 443
(again, you can use a different port, but your users will have to type port or you can use link translation with
products such as ISA).

So, you can have multiple SSL sites on one web server. You would
configure them on different IIS virtual servers with ports like 443,
4443, 4444, etc. Then, have link translation going; when a request is
received for, the person is directed to the web
server on port 4443, for example.

Change Application Pool on SharePoint IIS site

To change the application pool for an existing Windows SharePoint
Services site (IIS virtual server):
-Ensure that the new application pool is running under the same
identity the old AppPool is running as. (if you don’t, then SharePoint
may not be able to connect to the content or configuration database)
-In IIS, expand Web Sites.
-Right-click on the virtual server you want to change and select properties.
-On the ‘Home Directory’ tab, under the ‘Application settings’
section, change the ‘Application pool:’ to the new application pool
and click Apply, then OK.
-Back in the Internet Information Services Manager, expand the virtual
server you are changing by clicking the + sign beside the name.
-For every Virtual Directory (default virtual directories for a WSS
site are _layouts, _vti_bin, and _wpresources)under the website,
ensure they are running under the new application pool by:
–>Right-clicking on the virtual directory, select Properties.
–>Under the ‘Application settings’ section, change the ‘Application
pool:’ to the new application pool if necessary, and click Apply, then
-Reset IIS