What do you know. I always knew that ISNUMERIC would work with commas but assumed it was because we used them when we write in the real world and...

In the US at least, a comma is used every three places to make numbers easy to read. You passed in in essence "one hundred thousand, two hundred" as...

Uh, no...

100,200 is a real number. Just because it's in a character string doesn't change that. ISNUMERIC looks to see if whatever you pass it can be made...

Then script out the job, and add variables to the script for the path and the config file, and you can change the variables one time in that script. ...

I did read your code. You create two variables to indicate the path that the SSIS package is in as well as the path of the config file for...

A SQL Server Agent job running an SSIS package could be configured to point to a config file without a batch file. If all that the batch file is...

As far as the seed goes, this will report the seed:

DBCC CHECKIDENT ("FESD.dbo. Usernames ", NORESEED);

GO

And this will set the seed to 1:

DBCC CHECKIDENT ("FESD.dbo. Usernames ", RESEED, 1);

GO

However, this...

SharePoint. Just say no if you can. Ugh. What a beast, and worst of all, there is nothing you can do to tune it. We've been...

select name, MAX(logdate) from sysdtspackagelog

group by name

Better choice would be to create a job to run this (as a batch file) and schedule the Agent to run the job.

Check BOL for the REPLACE string function. This is what you want.

We had a similar problem with DR testing and log shipping. One thing you can do is to use WITH STANDBY on the log shipping instead of NORECOVERY if...

If recompiling it once helped but performance later degraded, maybe one way to band-aid the mess is WITH RECOMPILE so that the SP recompiles on every execution?

4000 logins a minute for a small company sounds exhorbitant to me. How many connections on average do you have at any time? At my last job, a...

At least use

SET TRANSACTION ISOLATION LEVEL READ COMMITTED

in your transactions. Total guarantee of data accuracy (though it will cause issues with concurrency if the transaction is too long)...