|
|
|
|
|
Total Hits: 245 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
With the release of SQL Server 2005, Microsoft also released SQL Server 2005 Express Edition. This is the free version of the SQL Server engine that existed in prior releases under the MSDE namesake. While there were several great enhancements with SQL Server 2005, one great change was the release of SQL Server Management Studio Express a GUI based management environment for this free version of the database engine. Although having a GUI to manage this version is great, one thing that is still...
|
|
|
|
Total Hits: 165 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
With most, if not all organizations, when executing processes during non business hours it is imperative to know if and when the these processes fail. At a minimum, full backups are typically executed off hours, but many organizations execute resource intensive batch processes which are critical to the core business for the subsequent day. With staff members stretched to meet numerous needs, validating that the jobs have executed successfully on a daily basis can be time consuming, but it is o...
|
|
|
|
Total Hits: 218 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
One of the things you can do with SQL Server 2000 is setup Operators to be notified when there is a job failure or an alert has been triggered that should notify your DBA team. The problem with setting up notifications for jobs is that you need to edit each and every job in order to turn on notifications. If you only have a few jobs this is not that much work, but if you have several jobs and have several servers making this change may take some time. In addition, if you are using Maintenance...
|
|
|
|
Total Hits: 210 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
One problem that people often have is a large number of SQL Agent jobs on their servers and they don't want to remove them because they are not exactly sure what the jobs are used for or why they were created. In most cases a lot of these jobs were created to run one time, but no one took the time to enter a description or better yet delete the job after it was run. So because of this you end up with a lot of extra scheduled jobs that you probably don't really need....
|
|
|
|
Total Hits: 177 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
SQL Server Agent is a useful tool to allow you to schedule reoccurring jobs to run on your server. Most of these jobs are usually maintenance type jobs or data loads, but this tool can be used to run any T-SQL code or even execute programs external to SQL Server. In addition to the ability to schedule jobs to run, SQL Server Agent also gives you the ability to see historical run information for the jobs as well as for each step within the jobs. This information is very helpful to have on hand...
|
|
|
|
Total Hits: 164 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
I am making a number of SQL Server security changes at the server and database level all at once, which is a problem in and of itself. I will be changing SQL Server service accounts, removing rights to BUILTIN\Administrators group, limiting specific user rights, moving to group based security, changing SQL Server Agent Job owners, etc. Nevertheless, I want to prevent as many issues as possible with so many simultaneous changes. One issue (of many) that I am concerned about is related to SQL Se...
|
|
|
|
Total Hits: 195 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
I have a set of SQL Server Jobs (transaction log backups, notification of business rules, etc.) that run every 5 minutes just about 24 hours a day. I seem to lose my SQL Server Job History in a few days and need this type of data to troubleshoot specific situations. It always seems like I lose this SQL Server Job related data when I need it most. I am trying to find the SQL Server Job that someone could have setup to delete from these tables and I only see the Jobs that my team created. I ha...
|
|
|
|
Total Hits: 202 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
One big issue with scheduled jobs is that they are often batch type jobs that take a significant amount of resources when they run. Another problem is that these jobs usually run during off hours such as nights or weekends, so there is no one to monitor the jobs resource usage. Without being around to monitor the job activity it is difficult to determine whether the jobs are running efficiently or not. Also, when batch jobs are first implemented they are often done with less data, so the resou...
|
|
|
|
Total Hits: 202 | Today: 0
|
Author: Edgewood Solutions Engineers
|
Rating:
|
|
As a portion of our backup and recovery process I need to disabled (or enable) all of our SQL Server Agent Jobs depending on the situation and the SQL Server instance. I know I can use the GUI to click through and make the changes, but on a number of our SQL Server instances we have 50+ jobs, so this is a monotonous task. Do you have any scripts to enable or disable all SQL Server Jobs? What about enabling or disabling all SQL Server Jobs by Job name or Job Category name?...
|
|
|
|
Total Hits: 681 | Today: 1
|
|
Rating:
|
|
When you run an UPDATE statement, and the connection's isolation level is set to READ UNCOMMITTED, you may receive the following error message:
Error: 644, Severity: 21, State: 6
Could not find the index entry for RID '%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'.
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencin...
|
|
|
|
Total Hits: 534 | Today: 0
|
|
Rating:
|
|
If a message fails validation or routing in Microsoft BizTalk Server 2004, the BizTalk Adapter for SQL Server rolls back the transaction, and the failed message is still in the source SQL database. The SQL adapter will pick it up again, and then try to process it. The processing fails again, and the transaction rolls back again. This problem creates a continuous loop.
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem t...
|
|
|
|
Total Hits: 1805 | Today: 1
|
Author: MSDN
|
Rating:
|
|
When you use Microsoft OLE DB Provider for SQL Server (OLEDBSQL) in ADO.NET, if you try to start more than one transaction in a session, you receive the following error message:
System.Data.OleDb.OleDbException: Cannot start more transactions on this session...
|
|
|
|
|
|
