What type of hardware are you running ? What type of SAN are you running ?

There are a few combinations that are prone to this.

Yes - this is possible.

You will need to install the 'Log Parser' from MS - it's free.

oh the following:

@cmd='"' +

is single quote double quote single quite

and

'"'

is also is single quote double quote single quite

It's kind of hard to see on the post

and yet another way ... using some good old fashioned DOS within SQL:

declare@cmdvarchar(1024)

select @cmd='"' +

'F:' + '&&' +--> drive letter to go to

'cd RMI' + '&&' +

'set path=c:\jdk1.6.0_10\bin' + '&&'...

Finally in print - Thanks Steve - ISO9001 ! (did my first one over 15 years ago)

If you have ISO9001 then SOX is kind of dumb (although Jeff has lots...

As DBAs we act as the 'stewards' of data - we are not the owners of the data.

However it is our collective responsibility to document concerns such as this and...

Lots of good stuff here. Pass-phrases really work well. They are virtually uncrackable.

Capitalization and letter/number substitution are cool as well when you mix in case sensitivity.

Personally, use 16 character...

please add me to the 'interested luist' as well 😀

after listening to that type of fix I think that it may be time to begin the search for a new application vendor ...

Here are a couple of backup options ...

- LiteSpeed

- Striping - http://www.sqlservercentral.com/Forums/Topic704434-357-1.aspx

Updates Statistics yup ... don't forget sp_recompile as well !

Just because you have good statistics does not mean the optimizer will use them ...

You have to 'force' plan recompilations !

performance mainly - due to bad statistics and index fragmentation are concerns.

Additionally, dependent on the characteristics of the system, having a window large enough to perform 'Update Statistics' and 'Index...

If you are executing SSMS from a location other than the SQL Server itself, check the client software versions on the server and the location you are executing SSMS from.

If...

I have not reached 50 billion row mark yet. However we have numerous (between 50-100)databases with tables that range in row counts in the 100's of millions to just shy...

To add to Jack's information - do not defragment or reindex tables less than 64k pages (one extent). Since they are stored on mixed extents it does nothing. Remember SQL...