Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gdeconto
Posting Yak Master
107 Posts |
 Posted - 2002-01-17 : 17:22:58
|
| Our webserver currently stores website stats in text log files. We use a website stats tool to analyse site usage, etc.What I would like to do is import ALL of the stats for ALL of our websites into SQL for more detailed analysis; ie to do reports that our website stats tool doesn't do or doesn't do well enough.Unfortunately, to make the problem more complicated, there have been a number of instances where the information stored changed; ie some website usage fields were added or removed. Also, sometimes the stats were stored daily and sometimes weekly and sometimes monthly.Has anyone out there done this sort of mish-mash import before?? Any advice on creating stored procedures to do this sort of conversion?? |
|
|
aiken
Aged Yak Warrior
525 Posts |
Posted - 2002-01-20 : 01:04:09
|
| Well, first, I think you're looking at BCP or DTS, maybe with some pre-processing. Shouldn't be difficult, just time consuming.Going forward, you can have IIS log directly to SQL. There are numerous articles and how-to's out there. The only problem, the way I see it, is that there is no way to log IIS session variables (so the feature is useless to me because I need to log user ID's with each page, and IIS doesn't do that natively).But if you're working off of the flat files anyways, definitely look at the log to SQL capability. And, for existing data, look at DTS and/or BCP.Cheers-b |
 |
|
|
gdeconto
Posting Yak Master
107 Posts |
Posted - 2002-01-23 : 11:59:35
|
| Thanks.I would log to one of our sql servers but am concerned about network conditions (a very busy server or ...) that might cause some of the information to be lost; if I log to the text files, there is very little that would prevent logging(short of GPF or no disk space).Anyhow, I have looked around the web and have found standard solutions for situations where the log files are very "vanilla" (ie the content is very standardized and no changes were made in the layout, etc).Looks like I will have to write a custom tool to do the conversion; oh well. |
|
|
|
|
|
|
|
|
importing IIS webserver logs into sql