June 11, 2009 11:00 AM
Posted by: Denny Cherry
ERRORLOG,
LOGIN,
Security,
SecurityFightClub,
SQL Server 2000,
SQL Server 2005,
SQL Server 2008Knowing who has been logging into your SQL Server is one of the key things to know about your SQL Server. It lets you know quite a bit about who’s using your server, and about who’s been trying to break into your SQL Server, and most importantly if they have succeeded.
Obviously you can...
May 11, 2009 11:00 AM
Posted by: Denny Cherry
distrib.exe,
Replication,
SQL Server 2000,
SQL Server 2005,
SQL Server 2008The official answer is to delete the subscriber and recreate it pushing a new snapshot to the subscriber.
The much quicker and easier method is as follows.
1. Stop the distribution agent on the machine that it's currently running on.
2. Disable the SQL Agent job that runs the distribution...
May 7, 2009 11:00 AM
Posted by: Denny Cherry
Replication,
SQL Server 2000,
SQL Server 2005,
SQL Server 2008This is a "it depends" sort of question.
These are my recommendations, your mileage may vary.
Your distributor is on the same system as your publisher - Pull is probably for you
Your Subscribers are a very high transaction count - Push is probably for you
You need to manually copy the...
March 12, 2009 11:00 AM
Posted by: Denny Cherry
Back To Basics,
Execution Plan,
Index Performance,
SQL,
SQL Server 2000,
SQL Server 2005,
SQL Server 2008All to often when helping people look at query performance problems I'll ask them to look at the execution plan, and see what it says. Most query performance problems can be resolved simply by looking at the execution plan and seeing where you need to add an index.
All to often I (and others)...
September 1, 2008 11:00 AM
Posted by: Denny Cherry
distrib.exe,
logread.exe,
OutputVerboseLevel,
Replication,
replmerg.exe,
snapshot.exe,
SQL Server 2000,
SQL Server 2005,
SQL Server 2008The error reporting in SQL Server Replication isn't all that great. This is a well known issue that pretty much everyone knows about. Something that I don't know if a whole lot of people know about, is that there is a way to get a lot more information from replication about what's going on, and...
July 22, 2008 11:00 AM
Posted by: Denny Cherry
Back To Basics,
BACKUP DATABASE,
SQL,
SQL Server 2000,
SQL Server 2005Now that you have objects created within your database, and data within the tables you need to secure your database in case of a server failure or accidental data deletion. This would be done by taking backups of the database. Backups are taken by using the BACKUP DATABASE command.
The...
June 10, 2008 6:39 PM
Posted by: Denny Cherry
Article,
Cache,
SQL Server 2000,
SQL Server 2005I've just published another tip over on SearchSQLServer.com. This one is titled SQL Server...
March 31, 2008 10:00 AM
Posted by: Denny Cherry
Back To Basics,
SQL,
SQL Server 2000,
SQL Server 2005,
SQL Server 2008,
T/SQL,
UPDATEAfter you've inserted the data into the table, it's time to update the data. We do this by using the UPDATE statement. The update statment can be used in two ways. The first is to update a record or set of records in a single table, by simply filtering the data in the table by using values...
