exec [dbo].[sp_BackupAllFull]

@MarkName nvarchar(8),

@BackupPath nvarchar(128),

@TimeStamp datetime = NULL,

@UseLocalTime bit=0

if you are trying to pass less parameters then procedure require and you omit some in middle you must...

maybe you can use deny permission ?

what about firewall settings ?

like others - i suggest "Inside SQL Server..." - these books are really good!

which version of SQL Server 2000 you are running ? SP4? later ?

rather then diagrams i suggest to use software like:

sql doc: http://www.red-gate.com/products/SQL_Doc/index.htm

or

apexsql doc: http://www.apexsql.com/sql_tools_doc.asp

i was using both, both are very good - but redgate tool is much...

Windows 2008 is really nice piece of software 😉

I'm running OLTP and DW systems on SQL/Windows 2008 x64 and they are running great!

it depends ;-))))

I assume that you gonna buy 16x SAS 73GB 15k rpm and you have only 1 production database

first of all: OS/SQL Binaries: 2disks -> RAID 1 -> 73GB...

which version of SQL you are running ? SP 4?

you are running which build of SQL ? SP4 or higher ?

yes, these problems occurs when IO is too slow to allocate new space. there is a good tip to set a smaller Auto-Grow indicator;

OR

a much better solution is to:

1)...

Steve try this...

declare @i int

set @i = 0

while (@i < 10000)

begin

set @i = @i + 1

print cast(@i as varchar)

begin tran

end

select @@TRANCOUNT

rollback

Some time % of disk time is ... not accurate as it should be. There are some better counters i.e. sec/read, sec/write - these should be less then 20ms (...

if you have an index on this column with date type a query like this:

select * from sys.databases

where DATEPART(year,create_date) = 2003

will be very slow (index scan is required here),...

maybe there is yet another trigger ?