Viewing 15 posts - 1,186 through 1,200 (of 1,539 total)
This link tells you on STANDBY clause when restoring via SSMS
http://msdn.microsoft.com/en-us/library/ms177429(SQL.90).aspx
This link gives u step by step guidance to setup up log shipping in STANDBY mode
June 14, 2009 at 1:03 pm
kirkwilson (6/14/2009)
The database is in a normal state.
If the database is in normal state, you cannot perform further restoration of log files.
The database must be either in NORECOVERY...
June 14, 2009 at 12:55 pm
kirkwilson (6/14/2009)
June 14, 2009 at 12:37 pm
sqlquestions15 (6/14/2009)
Need to Know about both the situation when Recovery Model is Simple and Full.
When the recovery mode is full, all transactions remain in the log file. You have to...
June 14, 2009 at 12:31 pm
sqlquestions15 (6/14/2009)
June 14, 2009 at 11:31 am
DBCC SHRHINKFILE shrinks a data or a log file.
Shrinking here pertains to reclaiming unused spaces within a file. There are operations that happen in the database that lead to growth...
June 14, 2009 at 11:21 am
using cursors might not be the best option but still using cursors in this example.
let us know if it's fine.
DECLARE @val4 varchar(20),@val1 varchar(20),@val2 varchar(50),@val3 varchar(50),@Sql varchar(8000);
set @val1='SQLSRV'
set @val4=CONVERT(VARCHAR(10), GETDATE(), 101)
Declare...
June 14, 2009 at 7:33 am
mcgillivrayk (6/14/2009)
June 14, 2009 at 7:21 am
I'm not sure if this is the most efficient code but perhaps does your work
select 'Begin XXOH_INV_INTERFACE_PKG.insert_trx(' +''''+ convert(varchar,getdate(),101) + ''''+
',' +''''+'SQLSRV' + '''' +',' + '''' + ...
June 14, 2009 at 6:09 am
christian.benvenuto (6/8/2009)
June 14, 2009 at 5:33 am
As suggested by Florian, there must be some variable (may be within sp), which is defined as CHAR datatype, where in the value in the variable is automatically padded with...
June 14, 2009 at 12:32 am
Please do not cross post. All replies can be given here:
http://www.sqlservercentral.com/Forums/Topic733582-145-1.aspx
June 13, 2009 at 11:49 pm
unless you have excessive amount of data getting inserted, most likely the cause is dbcc reindex.
Perhaps this link should help you.
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=112916
What i can think of is, DBCC REINDEX creates a...
June 13, 2009 at 11:11 pm
Are you sure your mdf grew or ldf? reindexing causes the log to grow heavily.
Also, if you have performed DBReindex after quite long time, chances are the file has grown...
June 13, 2009 at 10:41 pm
Viewing 15 posts - 1,186 through 1,200 (of 1,539 total)