Note: you might need to register at SQLServerCentral.com to gain access to the site to read the above linked article.

Here is a sample of what I did (this would all go on a single line)

c:\”program files”\”log parser 2.2″\LogParser -iCheckPoint:myCheckPoint.lpc -o:SQL -server:localhost -database:IISLogs -createtable:ON “SELECT * FROM ex0810*.log TO IISLogs”

This short command line will read in all log files that start with ex0810 and import them into a table called IISLogs.  It will also create a checkpoint file so that if you run the command again it will not import records that have already been imported.

How cool is that?

Once all the importing is done you can leverage the SQL tables using whatever methods you need to.

If you need any help with stuff, send us a note at support at quarksoft.com.

The way to accomplish this is to use the DBCC CHECKIDENT command.

For example:

DBCC CHECKIDENT (SalesForce, reseed, 0)

This assumes your table is called SalesForce and you want to start the numbering at 1.  If you wanted to start the number at 2000 you can substitute 0 with 1999.  There has been some discussion that has said if the table never had records added to it the reseed value itself will be used instead of the reseed + 1 value.  You should not need to use this statement for a “new” table.

Credit for this post is given to Pinal Dave over at http://sqlauthority.com/.  The specific post this I am referring to is the one at this page.

If you complete the following steps you can get a backup copy of the database on your local workstation (assuming you have SQL Server installed locally):

1. Get the IP address of your local computer using the ipconfig command or some other method.
2. Make sure you have created a share on your computer in the location where you want the backup file to be stored. For this example I am going to assume there is a share called BACKUP that points to C:\BACKUP (again, this share is on your local workstation, not the remote SQL Server)
3. Connect to the remote database with SSMS
4. Open a Query Window
5. Execute the following command (replace 1.1.1.1 with the IP address determined from step 1 and replace YourDatabase with the name of the database you want to backup)

BACKUP DATABASE YourDatabase
TO DISK = '\\1.1.1.1\Backup\YourDatabase.bak'
WITH FORMAT,
NAME = 'Full Backup of YourDatabase'

Now you can use SSMS to restore the database to your local copy of SQL Server or just keep it around in case you mess up the production database.

Another useful thing you can do is to schedule this and use the OSQL command line tool to execute the script as part of a development release or any other process. There are lots of options.

declare @year int, @month int, @day int
select @year = 2006, @month = 1, @day = 16

select dateadd(month,((@Year-1900)*12)+@Month-1,@Day-1)

This is especially useful when doing date comparisons in queries.  Many people use the convert function, but the above code executes far faster because it does not have to do any string manipulations.  Credit should be given to Michael Valentine Jones for this tip.  More information about this tip can be found here.  Here is some more great information on date manipulation for SQL Server.