Peer-to-Peer Questions #25: Install PPTP, Upgrade SQL Server, Index Server Cataloging, IIS Visitors
May 18, 2000
Editors Note This article, culled from the TechNet Web site (https://www.microsoft.com/technet), answers the most interesting questions received on the peer -to-peer discussion groups over the past few weeks. To post your own questions, visit the TechNet discussion groups at https://www.microsoft.com/technet/community/newsgroups/default.mspx.
This first question is from IT Pro Travis, and is about a feature in Windows NT 4.0—Point to Point Tunneling Protocol—that is not showing up as an option that can be installed. His question:
On This Page
Where in the World did my PPTP Go?
Upgrade SQL Server 6.5 to 7.0 and TempDB size
Index Server: Just Stops Cataloging!
Anonymous Internet User Accessing SQL Server – How to?
Where in the World did my PPTP Go?
Q: I recently wanted to install Point to Point <Tunneling> Protocol but I do not have that choice on one of my servers. What must I have to install PPTP? It is not in the list of installable protocols. Where did it disappear to?
Travis
A: IT Pro Todd makes a valiant try to assist:
I don't know this for sure, but a guess would be that it became available with one of the later service packs. Which SP are you at now?
Todd
Q: Travis replies with the just the thing that is needed to nail this problem down. Read on:
I am running it on an IBM p75 Model 730 and I have service Pack 6a installed.
Travis
A: Ahhhhh—the true nugget of information surfaces—we have a Microchannel computer here, don't we? Fortunately, there's an explanation about what's going on with this configuration, and is explained in the following Knowledge Base article:
Q168064: PPTP Protocol Not Available on MCA Computers
Regarding how/where/when is PPTP made available: From the PPTP FAQ on TechNet website:
Q: When And How Is PPTP Made Available?
A: PPTP is included at no additional cost in Windows NT Server 4.0 and Windows NT Workstation 4.0. Read the full Point-to-Point Tunneling Protocol (PPTP) FAQ.
More Info:
Next, we look at a fairly common issue that comes up when IT Pros attempt to upgrade SQL Server from version 6.5 to 7.0. One of the requirements is that the tempdb must be at least 10 MB in size. The Upgrade Wizard will check on this and will not proceed until tempdb is at least 10 MB.
Upgrade SQL Server 6.5 to 7.0 and TempDB size
Q: I am trying to upgrade from 6.5 to 7.0 but the database upgrade fails since SQL 7.0 requires that tempdb be at least 10 MB (currently 2 MB). Can someone please provide me with the proper T-SQL syntax to increase the size of tempdb?
Tim
A: Here is a very helpful response detailing the Transact SQL commands, posted by none other than Kalen Delaney, who just happens to be a co-author of Inside Microsoft SQL Server 7.0, one chapter of which is on TechNet: Optimizing Query Performance. You can take her answer to the bank. Here's what Kalen suggested:
You need to make sure there is free space on a device, so you might want to create a new device first:
DISK INIT
name = 'more_tempdb',
physname = '<drive>:full path name of a new file',
vdevno = 100 , -- you must choose an unused number less than 255;
-- run sp_helpdevice, and look in the description
size = 128000 -- to see what has been used already
<execute it>
if it succeeds, expand tempdb onto it:
ALTER DATABASE tempdb ON more_tempdb = 25
HTH,
Kalen Delaney, MCSE, SQL Server MCT, MVP
Well, I would offer that what Kalen suggests pretty much sums it up! Here are some additional resources that should help anyone contemplating an upgrade to SQL Server 7.0. There's one chapter from the SQL Server Resource Kit titled, Chapter 17 - Upgrading to SQL Server 7.0 that everyone should study prior to starting an upgrade from SQL Server version 6.x to 7.0.
I would propose that the entire document be studied, and there is one particular section that I wanted to focus on, since IT Pro Tim's question falls into the category of things to get ready before initiating the upgrade. Check out the section called Prepare the SQL Server 6.x Installation.
Here's one more technical paper that is a pretty good read: Converting Databases to MS SQL Server 7.0.
There are more articles dealing with upgrading SQL server to version 7.0 that are available on the TechNet web. Search TechNet by performing a "Title Only" query using: upgrade sql.
One last thing that you can do to find information on changing the size of tempdb on SQL Server 6.5. You've got SQL Server 7.0 already installed, waiting for the upgrade to happen. Open SQL Server 7.0 Books Online and perform a search using the following query:
how to change the size of tempdb
That will result in a few hits, one of which is a topic with just about the same name as the query.
Index Server: Just Stops Cataloging!
Next is a question about why Index Server is apparently acting in a random fashion. IT Pro David Miller is looking for some help, and fellow-IT Pro Charles Tichenor steps up to do just that. Way to go, Charles!
Q: We are having a problem with our Index Server catalogs. We currently have about 30 different catalogs with our largest holding over 70,000 text files. This week, index server has just started picking random catalogs and stops indexing them. When you look at it there are just "n/a"s across the board (under docs to filter, total docs etc.). Some catalogs only break down half way and list the total docs and docs to filter. However, the docs to filter never get filtered and just sit. As new text files are added to the catalog they are not indexed even though the "total docs" and "docs to filter" counter goes up.
I have been able to temporarily remedy the problem by rebooting index server but invariably this problem creeps up again throughout the day.
We are running IIS 4.0/INDEX SERVER/WINNT 4.0/ASP 2.0. Any help would be greatly appreciated.
David Miller
A: To this question, IT Pro Charles Tichenor provides his experiences with the following reply.
David, In my experience, I've seen this type of behavior two times:
Automatic virus detection software (such as McAfee). In this case you have to upgrade your virus software or disable virus detection on directories watched by IS.
Indexing network shares. In this case you have to reduce the value of the ForcedNetPathScanInterval Index Server registry value, or better yet, move your documents to a non-network directory.
Good luck.
Charles Tichenor
Anonymous Internet User Accessing SQL Server – How to?
Q: IT Pro Frank Grassens is stuck. He's trying to figure out what type of SQL Server login to create for anonymous IIS visitors that need access to his SQL Server. His conundrum:
I wonder why all books and examples concerning ASP in combination with SQL Server use the "sa" credentials without a password to retrieve data for web pages. Lesson one in SQL server is to change the password after installation and be very concerned about giving permissions to users. Am I missing something here?
Nowhere is a clue to find what kind of user I should create in the SQL database for the anonymous IIS visitors. I now consulted several sources like: MSDN, SQL Books online, Unlocking ASP, Teach Yourself Active Server Pages in 21 days, Teach Yourself MS SQL Server in 21 days, Learnasp, Aspalliance etc. etc.
Can someone please explain this basic administrative task?
Frank
A: IT guy C. E. Buttles has a pretty darn good (I think) response that helps Frank. Here it is:
No, you are correct about the sa password, but many places do not assign one. For simplicity, books, etc. use it <the sa login> without <a password> and readers are supposed to substitute their information where it is different than what is used in the examples.
As far as IIS is concerned, IIS creates an anonymous user when installed. Usually it is IUSER_<computername>. You can give this account permissions in SQL Server. In SQL Server 6.5, use the SQL Security Manager; in SQL Server 7.0, assign the user to an appropriate role, assuming you are using integrated security.
If you are using standard security in either version, you will need to create a login within SQL Server, then assign privileges. This will also affect your ASP apps in that the IIS anonymous user will not be able to access SQL Server unless the user has the same account name in SQL Server and you specify a trusted connection, supplying user name and password. This opens up some risks if anyone gets into your system and views your scripts.
Frank was generous enough to post a follow-up. Here it is:
Thanks for your help,
I created an IUSR_<computername> user in SQL Server and assigned a role and permissions. I then made an DSN with NT authentication. A nice thing is that in ASP the parameters UIC=;PWD=; are obsolete now. Just calling with dbconnection.open "DSN=<datasourcename>" is enough to do the job.
Good to read Frank's follow-up—thanks, Frank! I noticed one glaring omission from Frank's bibliography of technical sources, however. Can you guess what that other resource might be? Yes! It is the Microsoft Knowledge Base, sometimes affectionately known as "The KB" (sometimes it is called something entirely different, depending on your level of success with finding the exact information you're after!) The KB can be accessed on the Technical Information CD or from the following URL: https://search.support.microsoft.com/kb/c.asp.
I spent a moment in the KB and dug up the following article that reinforces C. E. Buttles's suggestions. Here's the article:
152828: IIS Queries to SQL Server Generate Error 1326
We at Microsoft Corporation hope that the information in this work is valuable to you. Your use of the information contained in this work, however, is at your sole risk. All information in this work is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Microsoft Corporation. Microsoft Corporation shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.