Viewing 15 posts - 1,396 through 1,410 (of 5,103 total)
when you restore a 2000 database in a 2005 the compatibility level is automatically 8.0
to verifyit run :
exec sp_dbcmptlevel @dbname = name
November 14, 2007 at 1:39 pm
And make sure that the drive is "compatible" with the controller you are using ... 😀
November 14, 2007 at 1:07 pm
Make sure you update your stats with "FULLSCAN" and that you rebuild your indexes.
After that the runaway plans can be revisited I have found only 2 cases in which the...
November 14, 2007 at 1:06 pm
As long as your filters are "narrow" enough and you are writting to an independent drive you should be fine!
November 14, 2007 at 1:03 pm
Funny thing is that RAW is what M$ uses for the tcp-E benchmarking.
November 14, 2007 at 11:58 am
If you make it too small you may suffer from autogrows so. You should size it properly so that you have the necessary space at all times and you need...
November 13, 2007 at 2:53 pm
Datamirror
SQL Server Log Shipping
SQL Server Replication
November 13, 2007 at 2:50 pm
you should ensure that the destination path exists:
restore filelistonly from disk='....'
See if the destination exists. Normally 2005 introduce MSSQL.1 in the path so it may not match the 2000 one...
November 13, 2007 at 2:49 pm
Tony Rogerson has found that "DISABLING" triggers (at least in 2000) does not disable the underlying performance effect entirely
http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/10/27/1248.aspx
So do NOT trust on Disabling when performance is at stake....
November 13, 2007 at 2:42 pm
It all depends what are you calling "corrupt" usually when corruption affects the primary replication agents break and you effectively can't transfer "corruption" ...
November 6, 2007 at 3:05 pm
You are correct on the SWICHT statement. It is not possible to use it because it is supposed to be a minimally logged opperation which LogReader can't understand, like Truncate...
November 6, 2007 at 3:03 pm
Those Services Operate only on the Local machine and there is no need to change that in fact is possibly the only way to ensure transparent access to VSS.
You should...
November 6, 2007 at 2:52 pm
CREATE TABLE tbl_PaymhistCurrentWeek
( AcctCode AS ISNULL(SUBSTRING(AcctCodeWithZeros, PATINDEX('%[^0]%', AcctCodeWithZeros), 14),''),
Co char(2) Not Null,
AcctCodeWithZeros varchar(20) Null,
CONSTRAINT PK_PaymhistCurrentWeek Primary Key Clustered
(AcctCode, Co)
)
Insert into tbl_PaymhistCurrentWeek (Co, AcctCodeWithZeros) VALUES ('C1','0000123')
Insert into tbl_PaymhistCurrentWeek (Co, AcctCodeWithZeros)...
November 1, 2007 at 9:14 am
Also make sure you don't do just one INSERT per row but per "multiple" rows.
October 31, 2007 at 3:44 pm
Viewing 15 posts - 1,396 through 1,410 (of 5,103 total)