Thursday, March 29, 2012
automating the dumping of databaser in sql server 6.5
to automate the dumping of databases at a preset interval. I can do
it manually and do so each day but it would be nice if it would do it
on its own.
thanksHi,
You can Schedule this using the "Schedule Tasks" available in SQL Server 6.5
Enterprise manager.
THis schedule tasks will be ran by the service "SQL Executive", so ensure
that the service is up all the time.
How to do:-
1. Open enterprise manager
2. COnnect to the server
3. In the menu ,choose Server option and select "Scheduled tasks"
4. Click the first Icon (New Task)
5. Give the name as "Backup" and then select the type as "TSQL".
6. In the command type your "DUMP DATABASE COMMAND"
7. In the schedule option click "Recurring"
8. Click the change command button and select the intervals and days to
schedule
9. CLick ok
Thanks
Hari
MCDBA
<kg7poe@.yahoo.com> wrote in message
news:lcala0t54hin158dlsqtq9bka6k4f5b5ke@.4ax.com...
> I don't happen to have any sql server 6.5 books. I need to know how
> to automate the dumping of databases at a preset interval. I can do
> it manually and do so each day but it would be nice if it would do it
> on its own.
> thanks
>sql
automating the dumping of databaser in sql server 6.5
to automate the dumping of databases at a preset interval. I can do
it manually and do so each day but it would be nice if it would do it
on its own.
thanks
Hi,
You can Schedule this using the "Schedule Tasks" available in SQL Server 6.5
Enterprise manager.
THis schedule tasks will be ran by the service "SQL Executive", so ensure
that the service is up all the time.
How to do:-
1. Open enterprise manager
2. COnnect to the server
3. In the menu ,choose Server option and select "Scheduled tasks"
4. Click the first Icon (New Task)
5. Give the name as "Backup" and then select the type as "TSQL".
6. In the command type your "DUMP DATABASE COMMAND"
7. In the schedule option click "Recurring"
8. Click the change command button and select the intervals and days to
schedule
9. CLick ok
Thanks
Hari
MCDBA
<kg7poe@.yahoo.com> wrote in message
news:lcala0t54hin158dlsqtq9bka6k4f5b5ke@.4ax.com...
> I don't happen to have any sql server 6.5 books. I need to know how
> to automate the dumping of databases at a preset interval. I can do
> it manually and do so each day but it would be nice if it would do it
> on its own.
> thanks
>
|||"kg7poe@.yahoo.com" wrote:
> I don't happen to have any sql server 6.5 books. I need to know how
> to automate the dumping of databases at a preset interval. I can do
> it manually and do so each day but it would be nice if it would do it
> on its own.
> thanks
>
automating the dumping of databaser in sql server 6.5
to automate the dumping of databases at a preset interval. I can do
it manually and do so each day but it would be nice if it would do it
on its own.
thanksHi,
You can Schedule this using the "Schedule Tasks" available in SQL Server 6.5
Enterprise manager.
THis schedule tasks will be ran by the service "SQL Executive", so ensure
that the service is up all the time.
How to do:-
1. Open enterprise manager
2. COnnect to the server
3. In the menu ,choose Server option and select "Scheduled tasks"
4. Click the first Icon (New Task)
5. Give the name as "Backup" and then select the type as "TSQL".
6. In the command type your "DUMP DATABASE COMMAND"
7. In the schedule option click "Recurring"
8. Click the change command button and select the intervals and days to
schedule
9. CLick ok
Thanks
Hari
MCDBA
<kg7poe@.yahoo.com> wrote in message
news:lcala0t54hin158dlsqtq9bka6k4f5b5ke@.
4ax.com...
> I don't happen to have any sql server 6.5 books. I need to know how
> to automate the dumping of databases at a preset interval. I can do
> it manually and do so each day but it would be nice if it would do it
> on its own.
> thanks
>|||"kg7poe@.yahoo.com" wrote:
> I don't happen to have any sql server 6.5 books. I need to know how
> to automate the dumping of databases at a preset interval. I can do
> it manually and do so each day but it would be nice if it would do it
> on its own.
> thanks
>
Sunday, February 19, 2012
auto-commit vs begin transaction overhead
We have an application that has problems with deadlocks. Part of our strategy in handling these deadlocks is resubmitting the transaction. My solution to this part of the strategy is to wrap every storedprocedure in a transaction so this would include reads and writes. My architect has raised some concerns with regard to performance if it's implemented this way. I've come across documentation (http://msdn2.microsoft.com/en-us/library/ms187878.aspx) in the sql server 2005 books online that auto-commit happens on every statement anyway but haven't come across anything that explicitly states the performance penalty if there is one. Is there difference in overhead between calling 'BeginTransaction' for every statement or just letting auto-commit do it's magic. Is this implemented in SqlClient object or at a database level?Some folks from the database engine team would be best suited to answer your question re: auto-commit vs. explicit transaction performance. Depending on their answer, you might also want to follow up with folks in the .Net Data Access and Storage forum to ensure there are no performance implications in the particular client that you are using.|||
AFAIK, definetely there is an overhead. And how much overhead depends on the traffic on your application, and the size of the DB.
There will be lot of contention since transactions will keep the locks until the transaction commits. You might see slow down in your transaction times. If you have a web form and a submit button, you keep the user waiting longer for his transaction to commit if there are more transactions waiting. Also, there could be timeout issues. Your CPU could shoot up. If you use #temp tables your tempDB could blow up.
If you have dead lock scenarios I would look into which procs cause it and fix them rather than wrap every T-SQL with a transaction.
And if you really want to measure the overhead, you can use some 3rd party tools like NetIQ and do a load test and quantify the results.
Thursday, February 16, 2012
Auto Stats
SP3a).
Does it take any database or other locks at all ? So that it could
contribute to a timeout/disconnect problem we are getting ?
I don't believe so. I think it's unlikely that that is contributing to
any timeout problem, but you can always disable that option (ALTER
DATABASE <dbname> SET AUTO_UPDATE_STATISTICS OFF) and see if the timeout
problem goes away (just do the statistics updates manually (EXEC
sp_updatestats) out of hours).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Jim Trowbridge wrote:
>Books Online does not explain how this runs for SQL Server 2000 (we are on
>SP3a).
>Does it take any database or other locks at all ? So that it could
>contribute to a timeout/disconnect problem we are getting ?
>
>
Auto Stats
SP3a).
Does it take any database or other locks at all ? So that it could
contribute to a timeout/disconnect problem we are getting ?This is a multi-part message in MIME format.
--010006090901020804020402
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
I don't believe so. I think it's unlikely that that is contributing to
any timeout problem, but you can always disable that option (ALTER
DATABASE <dbname> SET AUTO_UPDATE_STATISTICS OFF) and see if the timeout
problem goes away (just do the statistics updates manually (EXEC
sp_updatestats) out of hours).
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Jim Trowbridge wrote:
>Books Online does not explain how this runs for SQL Server 2000 (we are on
>SP3a).
>Does it take any database or other locks at all ? So that it could
>contribute to a timeout/disconnect problem we are getting ?
>
>
--010006090901020804020402
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>I don't believe so. I think it's unlikely that that is
contributing to any timeout problem, but you can always disable that
option (ALTER DATABASE <dbname> SET AUTO_UPDATE_STATISTICS OFF</tt><tt>)
and see if the timeout problem goes away (just do the statistics
updates manually (EXEC sp_updatestats) out of hours).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Jim Trowbridge wrote:
<blockquote cite="mid92C390C7-7B08-412E-9053-16C8E295AFBD@.microsoft.com"
type="cite">
<pre wrap="">Books Online does not explain how this runs for SQL Server 2000 (we are on
SP3a).
Does it take any database or other locks at all ? So that it could
contribute to a timeout/disconnect problem we are getting ?
</pre>
</blockquote>
</body>
</html>
--010006090901020804020402--
Auto Stats
SP3a).
Does it take any database or other locks at all ? So that it could
contribute to a timeout/disconnect problem we are getting ?I don't believe so. I think it's unlikely that that is contributing to
any timeout problem, but you can always disable that option (ALTER
DATABASE <dbname> SET AUTO_UPDATE_STATISTICS OFF) and see if the timeout
problem goes away (just do the statistics updates manually (EXEC
sp_updatestats) out of hours).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Jim Trowbridge wrote:
>Books Online does not explain how this runs for SQL Server 2000 (we are on
>SP3a).
>Does it take any database or other locks at all ? So that it could
>contribute to a timeout/disconnect problem we are getting ?
>
>