Disk Stats

I'm relatively new to Perf Mon and am trying to figure out
the best disk objects to use. I've been watching our
servers and I've noticed that sometimes in the evening the
Avg Disk Q Length goes over acceptable levels. But during
the entire night (or most of it) the Total MBytes/Second
is very high due to backups apparently.
How can I interpret these two numbers? One says the
server is getting slammed all night and the ohter says
it's only having troubles occasionally? Which do I go by?
Dan,
Having high values for Total MBytes/Second is not necessarily bad, all it
indicates is that you're getting good I/O throughput.
However, Avg Disk Queue Length can be a sign of problems, especially when it
gets into the hundreds, because it is indicating that the I/O system cannot
keep up with requests.
For advice on the best SQL Server PerfMon counters for disk I/O, see Tom
Davidson's articles in SQL Magazine.
Hope this helps,
Ron
Ron Talmage
SQL Server MVP
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:017601c4a00a$51af0c00$a401280a@.phx.gbl...
> I'm relatively new to Perf Mon and am trying to figure out
> the best disk objects to use. I've been watching our
> servers and I've noticed that sometimes in the evening the
> Avg Disk Q Length goes over acceptable levels. But during
> the entire night (or most of it) the Total MBytes/Second
> is very high due to backups apparently.
> How can I interpret these two numbers? One says the
> server is getting slammed all night and the ohter says
> it's only having troubles occasionally? Which do I go by?

Disk Stats

I'm relatively new to Perf Mon and am trying to figure out
the best disk objects to use. I've been watching our
servers and I've noticed that sometimes in the evening the
Avg Disk Q Length goes over acceptable levels. But during
the entire night (or most of it) the Total MBytes/Second
is very high due to backups apparently.
How can I interpret these two numbers? One says the
server is getting slammed all night and the ohter says
it's only having troubles occasionally? Which do I go by?Dan,
Having high values for Total MBytes/Second is not necessarily bad, all it
indicates is that you're getting good I/O throughput.
However, Avg Disk Queue Length can be a sign of problems, especially when it
gets into the hundreds, because it is indicating that the I/O system cannot
keep up with requests.
For advice on the best SQL Server PerfMon counters for disk I/O, see Tom
Davidson's articles in SQL Magazine.
Hope this helps,
Ron
--
Ron Talmage
SQL Server MVP
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:017601c4a00a$51af0c00$a401280a@.phx.gbl...
> I'm relatively new to Perf Mon and am trying to figure out
> the best disk objects to use. I've been watching our
> servers and I've noticed that sometimes in the evening the
> Avg Disk Q Length goes over acceptable levels. But during
> the entire night (or most of it) the Total MBytes/Second
> is very high due to backups apparently.
> How can I interpret these two numbers? One says the
> server is getting slammed all night and the ohter says
> it's only having troubles occasionally? Which do I go by?sql

Discovering SQL Server Object Dependencies

Apart from it being one of the features advertised by TOAD, where else
might I be able to find tools for displaying the dependencies between
objects. A node-based viewer (eg tree control) would be ideal. Does
any such tool exist?Hi Kofi
http://www.ag-software.com is one option.
Regards,
Greg Linwood
SQL Server MVP
"Kofi" <kofisarfo@.gmail.com> wrote in message
news:5c157557.0405130109.12ccc481@.posting.google.com...
> Apart from it being one of the features advertised by TOAD, where else
> might I be able to find tools for displaying the dependencies between
> objects. A node-based viewer (eg tree control) would be ideal. Does
> any such tool exist?

Disconnecting from engine does not closes database

I connect Managment Studio to MSDE 2000SP4.

Open database, open some object, then disconnect from engine (not simple collapse DB objects). In other programm try to drop database. Until you don't close MSSQL MStudio, database is in use.

In older version collapsing DB objects in tree closes DB.

Hi!

I don't have access to MS from 2000SP4, but I can tell you that MS in SQL2005 have Disconnect command in context menu of the server node. I think this is what you need.

|||Does not matter what engine you use. I wrote, that when I DISCONNECT (using this command from menu - this is one way) from engine, database is in use while MS running. So, MS does not disconnect from DB, only delete engine from list.|||Strange, when you Disconnect from server, it must lost connection and must release locks on any DB that was locked.|||

Please, read my first post and try to reproduce it. After disconnecting, try to drop database you used in SSMS. Open new query in SSMS and try. "Cannot drop..."

It's not strange, IT IS A BUG.

|||I have "Drop connections" checkbox for that case. It works in SQL2000 and I see it in SQL2005.|||

Where did you see this checkbox in SSMS?

May be this checkbox exists (I don't find it, but when I DISCONNECT from server all objects incl DB MUST be CLOSED.

I had no this problem in SQL2000 cause database was auto closed after collapsing it's objects in tree and when it wasn't selected in tree.

|||

I have it in window that appears after "Detach" command. Also I remember there was switch "Auto close" in SQL2000 Enterprise Manager (last tab in DB properties).

Perhabs this is MSDE behavior? I run on SQL Server and don't use MSDE for a long time.

|||

I don't need detach database.

Autoclose is a DB property (must NOT overrides by SSMS) and it's "TRUE". And Autoclose have another purpose - it closes DB after all users disconnects.

I had try with Autoclose = True and AC = false. Result: Cannot drop database.

There is no difference between MSSQL and MSDE for such things.

May be you'll try?

|||Please, describe steps to reproduce, I will try it.

Disaster Recovery

Whilst importing some procedures, I have left the
'Transfer Dependent Object' checked and the 'Drop Destination Objects'
result I have over-written certain tables
Can it be undone with the
transaction log and if so How ?
regards EarnieIf you have a backup of your target database, prior to the overwrite,
restore it. Or restore it with a different name, and copy the objects you
need.
In case of no backup, you can use a tool like Lumigent Log Explorer to undo
those changes.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Earnie" <Earnie@.discussions.microsoft.com> wrote in message
news:EADFAF0B-FD14-4937-9F6D-98DFAE297CFF@.microsoft.com...
Whilst importing some procedures, I have left the
'Transfer Dependent Object' checked and the 'Drop Destination Objects'
result I have over-written certain tables
Can it be undone with the
transaction log and if so How ?
regards Earnie|||Assuming you have valid database and log backups, use the STOPAT option
to restore the log to a point in time before the tables were droppped.
David Portas
SQL Server MVP
--

Disabling SQL 2005 Case Sensitive

In SQL 2005 is there a way of disabling the case sensitive option for
database objects and data criteria at the database or server level?
Case sensitivity are determined by the collation. When you install SQL Server, you specify a
collation, which:
Acts as default for a new database.
Is the collation for the system databases.
When you create a new database, you either define a collation or don't. If you don't, you inherit
what you selected when you installed. This collation is the default collation for the database.
When you create a table, you can at the column level specify collation. If you don't, you get the
database default collation.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2000cwe.googlegrou ps.com...
> In SQL 2005 is there a way of disabling the case sensitive option for
> database objects and data criteria at the database or server level?
>

Disabling SQL 2005 Case Sensitive

In SQL 2005 is there a way of disabling the case sensitive option for
database objects and data criteria at the database or server level?Case sensitivity are determined by the collation. When you install SQL Serve
r, you specify a
collation, which:
Acts as default for a new database.
Is the collation for the system databases.
When you create a new database, you either define a collation or don't. If y
ou don't, you inherit
what you selected when you installed. This collation is the default collatio
n for the database.
When you create a table, you can at the column level specify collation. If y
ou don't, you get the
database default collation.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2000cwe.googlegroup
s.com...
> In SQL 2005 is there a way of disabling the case sensitive option for
> database objects and data criteria at the database or server level?
>|||In 2005 is their a way of resetting the server value after it has been
installed?
Tibor Karaszi wrote:[vbcol=seagreen]
> Case sensitivity are determined by the collation. When you install SQL Ser
ver, you specify a
> collation, which:
> Acts as default for a new database.
> Is the collation for the system databases.
> When you create a new database, you either define a collation or don't. If
you don't, you inherit
> what you selected when you installed. This collation is the default collat
ion for the database.
> When you create a table, you can at the column level specify collation. If
you don't, you get the
> database default collation.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2
000cwe.googlegroups.com...|||You have to rebuild the system database, which mean that all information in
the system databases are
lost. Use setup.exe for this (details in Books Online). Then you have to att
ach or restore all user
databases, and of course detach or backup those first. The user databases wi
ll have the same
collation as before the rebuild.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161877957.117735.3190@.f16g2000cwb.googlegroup
s.com...
> In 2005 is their a way of resetting the server value after it has been
> installed?
> Tibor Karaszi wrote:
>

Disabling SQL 2005 Case Sensitive

In SQL 2005 is there a way of disabling the case sensitive option for
database objects and data criteria at the database or server level?Case sensitivity are determined by the collation. When you install SQL Server, you specify a
collation, which:
Acts as default for a new database.
Is the collation for the system databases.
When you create a new database, you either define a collation or don't. If you don't, you inherit
what you selected when you installed. This collation is the default collation for the database.
When you create a table, you can at the column level specify collation. If you don't, you get the
database default collation.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2000cwe.googlegroups.com...
> In SQL 2005 is there a way of disabling the case sensitive option for
> database objects and data criteria at the database or server level?
>|||In 2005 is their a way of resetting the server value after it has been
installed?
Tibor Karaszi wrote:
> Case sensitivity are determined by the collation. When you install SQL Server, you specify a
> collation, which:
> Acts as default for a new database.
> Is the collation for the system databases.
> When you create a new database, you either define a collation or don't. If you don't, you inherit
> what you selected when you installed. This collation is the default collation for the database.
> When you create a table, you can at the column level specify collation. If you don't, you get the
> database default collation.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <robin9876@.hotmail.com> wrote in message news:1161686322.061321.14570@.e3g2000cwe.googlegroups.com...
> > In SQL 2005 is there a way of disabling the case sensitive option for
> > database objects and data criteria at the database or server level?
> >|||You have to rebuild the system database, which mean that all information in the system databases are
lost. Use setup.exe for this (details in Books Online). Then you have to attach or restore all user
databases, and of course detach or backup those first. The user databases will have the same
collation as before the rebuild.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<robin9876@.hotmail.com> wrote in message news:1161877957.117735.3190@.f16g2000cwb.googlegroups.com...
> In 2005 is their a way of resetting the server value after it has been
> installed?
> Tibor Karaszi wrote:
>> Case sensitivity are determined by the collation. When you install SQL Server, you specify a
>> collation, which:
>> Acts as default for a new database.
>> Is the collation for the system databases.
>> When you create a new database, you either define a collation or don't. If you don't, you inherit
>> what you selected when you installed. This collation is the default collation for the database.
>> When you create a table, you can at the column level specify collation. If you don't, you get the
>> database default collation.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> <robin9876@.hotmail.com> wrote in message
>> news:1161686322.061321.14570@.e3g2000cwe.googlegroups.com...
>> > In SQL 2005 is there a way of disabling the case sensitive option for
>> > database objects and data criteria at the database or server level?
>> >
>

Disabled sp_oacreate in sql 2000?

Hi all,
I have an issue where a SQL server (2000 SP3a) is not executing
external objects. I have granted permissions to all sp_oa* stored
procedures as well as xp_cmdshell; I also ensured read/execute access
is enabled for Everyone on wscript.exe/dll. I am running the following
as 'sa':
DECLARE @.pid int, @.hr int, @.path varchar(500)
SET @.path = 'd:\public\\script\job.wsf'
EXEC @.hr = sp_OACreate 'WScript.Shell', @.pid OUT
EXEC @.hr = sp_OAMethod @.pid, 'Run', NULL, @.path
EXEC @.hr = sp_OADestroy @.pid
Command completes successfully, but the script never executes. I
have tryed with other objects and same result. I can see in Profiler
the script executes fine, but Windows Script Host never gets invoked.
This works on one server but not another; a third party hosting
facility installed the OS and DB but I'm not sure what they have
disabled, etc. or how to enable this. I know they've played with
security policies and registry settings but don't know what fixes this
issue.
Any help is greatly appreciated. Have a super day!
> Rich NorgaardDoes it work when you are logged in with sysadmin permissions? I'm thinking the proxy account
config...
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Rich" <richnorgaard@.hotmail.com> wrote in message
news:447699bb.0310151115.268b1c5c@.posting.google.com...
> Hi all,
> I have an issue where a SQL server (2000 SP3a) is not executing
> external objects. I have granted permissions to all sp_oa* stored
> procedures as well as xp_cmdshell; I also ensured read/execute access
> is enabled for Everyone on wscript.exe/dll. I am running the following
> as 'sa':
> DECLARE @.pid int, @.hr int, @.path varchar(500)
> SET @.path = 'd:\public\\script\job.wsf'
> EXEC @.hr = sp_OACreate 'WScript.Shell', @.pid OUT
> EXEC @.hr = sp_OAMethod @.pid, 'Run', NULL, @.path
> EXEC @.hr = sp_OADestroy @.pid
> Command completes successfully, but the script never executes. I
> have tryed with other objects and same result. I can see in Profiler
> the script executes fine, but Windows Script Host never gets invoked.
> This works on one server but not another; a third party hosting
> facility installed the OS and DB but I'm not sure what they have
> disabled, etc. or how to enable this. I know they've played with
> security policies and registry settings but don't know what fixes this
> issue.
> Any help is greatly appreciated. Have a super day!
> > Rich Norgaard