In all of our development projects, we have a batch script which concatenates all of the Sql scripts so the we can recreate the database with all the tables, default data and testing data in a single click.
The script file usually looks something like this:
set OUT=MASTER.SQL
del %OUT%
type Drop.sql Delimiter.txt >> %OUT%
type CreateTypes.sql Delimiter.txt >> %OUT%
type Create.sql Delimiter.txt >> %OUT%
type Procedures.sql Delimiter.txt >> %OUT%
type StartupData.sql Delimiter.txt >> %OUT%
type DefaultData.sql Delimiter.txt >> %OUT%
type TestData.sql Delimiter.txt >> %OUT%
isqlw.exe -dDbName -E -f %OUT%
In Sql Server 2005, the isqlw.exe command is replaced with the Sql Management Studio. The isqlw.exe line now looks like:
sqlwb -nosplash -d DbName %OUT%
Note that there must a space between the -d and the database name.
Wednesday, February 01, 2006
Thursday, November 17, 2005
AOL Spam Blocking - An Amazing Tale
It is getting harder and harder to run an independent mail server.
For the n'teenth time in the last 2 years, AOL has blocked my local e-mail server for sending spam to an AOL account. We host e-mail for my small company and a number of local, environmental organizations. Usually, AOL automatically removes the block after a day or so. This time, after about 10 days, we realized it was not coming back.
Tue 2005-11-15 10:43:09: <-- 554-: (RLY:CH) http://postmaster.info.aol.com/errors/554rlych.html
Tue 2005-11-15 10:43:09: <-- 554 TRANSACTION FAILED Tue 2005-11-15
As it turns out, the spam was coming though our server because one of our users had forwarded their local e-mail account to their personal, AOL account. Also, the user was marking the incoming messages as spam when they accessed their AOL account.
Here is the amazing part: I found a contact number for the AOL Postmaster and a live person answered the phone without having to navigate a maze of phone options. Not only that, but the person that answered was polite and extremely helpful! (Ok, it seemed amazing to us at the time).
We are having a similar issue with AT&T Worldnet and are waiting for a response from them. The bottom line is that we no longer allow automatic mail-forwarding from our server.
For the n'teenth time in the last 2 years, AOL has blocked my local e-mail server for sending spam to an AOL account. We host e-mail for my small company and a number of local, environmental organizations. Usually, AOL automatically removes the block after a day or so. This time, after about 10 days, we realized it was not coming back.
Tue 2005-11-15 10:43:09: <-- 554-: (RLY:CH) http://postmaster.info.aol.com/errors/554rlych.html
Tue 2005-11-15 10:43:09: <-- 554 TRANSACTION FAILED Tue 2005-11-15
As it turns out, the spam was coming though our server because one of our users had forwarded their local e-mail account to their personal, AOL account. Also, the user was marking the incoming messages as spam when they accessed their AOL account.
Here is the amazing part: I found a contact number for the AOL Postmaster and a live person answered the phone without having to navigate a maze of phone options. Not only that, but the person that answered was polite and extremely helpful! (Ok, it seemed amazing to us at the time).
We are having a similar issue with AT&T Worldnet and are waiting for a response from them. The bottom line is that we no longer allow automatic mail-forwarding from our server.
Subscribe to:
Posts (Atom)