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:

http://msd2d.com/newsletter_tip.aspx?section=sharepoint&id=cd3fd32d-b989-4bff-aae7-a65846b795b6

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
far:

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 site.dev.domain.com , site.qa.domain.com,
site.domain.com as you go through devlopment, testing, and production
environments.

Also, you have to understand how IIS works. It receives a request for
“domain.com” 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 domain.com (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
error.

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
domain.com:new 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
https://domain.com:new 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 https://site1.com, 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
OK.
-Reset IIS

Mapping a Window’s share to a SharePoint site

You can map a network share to a SharePoint site (or individual
document library) doing the following:

net use s: http://sharePointserver/somesite/doclib

Note that if there is a space in the path, you need to use quotes
around the url:

net use s: “http://sharePointserver/somesite/shared documents”

Also need to ensure the WebClient service is running.
This would be really useful for automated uploading of documents
through scripts, etc.

Sources:
(http://www.sharepointu.com/forums/m_18100/mpage_1/key_//tm.htm#18872)

Moving WSS SQL databases to a new SQL server

1-Copy the databases from the old SQL server to the new one.
2-Then, in the config database on the new SQL server, open the Servers
table in the config database.
3-Change the Name and Address fields that have the old SQL server name
to the new SQL server name.
4-Open the SharePoint Central Administration page and click on “Set
configuration database server” under the Server Configuration section.
5-Change old SQL server name to new SQL server name. Click OK.
6-Again on the SharePoint Central Administration page, click on
“Configure virtual server settings”, and then click on a website you
want to change.
7-Click on “Manage content databases” under Virtual Server Management.
8-Click “Add a content database” and then ensure “Specify database
server settings” is selected.
9-Enter the SQL server name and database name. Enter 100 for each of
the following boxes and click OK. (Notice the content database that
was already there will have a 0 under the “Current Number of Sites”
column. This is because SharePoint realizes you are trying to
substitute. You can then remove the old database from the WSS list.)

Repeat steps 6-9 for any additional sites.
I know there are several steps, but it is truly the easy way. It goes
much smoother than any other way (in my experience).
Ensure the account used for the Application Pool has rights to the
databases (both config and any content db).
Note: Editing SharePoint databases can make your configuration ‘unsupported’ by Microsoft