Viewing 15 posts - 6,376 through 6,390 (of 7,489 total)
"Change your recovery option to Simple this will prevent the log from capturing all the data and filling up" ....
Nop.![]()
It will depend on your...
February 9, 2006 at 5:31 am
Log files will only shrink up to the last active log chunk.
so it may be needed to run the shrink-file x-times. ![]()
-- Shrink_TrxLog.SQL
--INF:...
February 9, 2006 at 4:56 am
Maybe you'll find some script a the SSC-scripts section. ![]()
Here's one I install by default for dev-support :
-- it uses the msdb-tables and will...
February 9, 2006 at 4:52 am
aha, the trigger issue ![]()
That's exactly the reason why one should always evaluate if a "procedure" should _always_ be executed when modifying data for...
February 9, 2006 at 12:11 am
... I love stuff like this. Maybe you should submit it to the script library! ...
Done ![]()
February 8, 2006 at 3:15 am
select
sum(BalAmt), -- sum does not use columns that have a null-status ![]()
sum(BalIntRate)
from DebtCurrBal c with(nolock)
join DebtBase d with(nolock)
on c.DebtBaseKey =...
February 8, 2006 at 2:57 am
check your execution plan !
I presume sqlserver in scanning
your full table and suffers a bunch of waits !
"RowId is unique index" Is...
February 8, 2006 at 2:53 am
I've reinstalled my test-dekstop with winxp sp2, added sql2000 client (no sp) and then sql2005 client.
Everithing works fine.
SQL2005 client is being instaled with these options :
ADDLOCAL=Client_Components,Connectivity,SQL_Tools90
,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy
,SQL_Documentation,SQL_BooksOnline,SQL_Samples
February 8, 2006 at 12:47 am
if this connection is to be used frequently , maybe enabling connection pooling is an option
control panel\data sources\connection pooling ....
This way your connection is kept alive (after the application...
February 7, 2006 at 8:01 am
So apparently the problem is related to the speed of building a connection
or it might even be a connectionpooling problem.
February 7, 2006 at 7:26 am
Do you use a domain service account for sqlserver ?
0x80004005 is always an access problem
February 7, 2006 at 7:12 am
nice example ![]()
Here is another :
WITH
cteEmployeeOrderedByMyRowNumber AS
(SELECT ROW_NUMBER()
February 7, 2006 at 4:03 am
check your sqlagent properties/ jobsystem and raise the jobhistory lines.
afaik there is no way of stating that each job should retain at least the last month or n-days of execution...
February 7, 2006 at 3:02 am
What's DBCC CHECKDB stating ?
Also check out : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=197066 ![]()
and http://www.portsense.com/ng/microsoft.public.sqlserver.server/2004/March/22/314579.cfm
February 6, 2006 at 6:55 am
Just a wild shot :
What (type of) account is serving Scheduled Task ? Maybe it does not have the authority to access the batch or osql
February 6, 2006 at 5:57 am
Viewing 15 posts - 6,376 through 6,390 (of 7,489 total)