Viewing 15 posts - 1 through 15 (of 213 total)
i fixed myself the new machines did not have the
c:\users\temp directory
got to love microsoft
October 25, 2013 at 7:45 am
it should have said will this work
i have commented in dynamic sql all the time
😉
August 13, 2012 at 2:52 pm
SQLRNNR (1/19/2012)
Trey Staker (7/22/2010)
January 19, 2012 at 9:24 am
Error Occurred Calling Object: ODSOLE Extended Procedure sp_OADestroy usage: ObjPointerToBeDestroyed int IN.
copying the exact info from the last post
word application
spellcheck
January 16, 2012 at 2:57 pm
http://www.sqlservercentral.com/articles/Editorial/77292/
didnt phil factor say PS is going bye to
January 16, 2012 at 2:21 pm
i saw that earlier too
but everytime i run it i get
on all 3 calls
ODsole extended procedure error
January 16, 2012 at 2:15 pm
thanks i found that:-P
but i dont see how to make the connection (everything i have tried gives me error :unsure:
EXEC @hr= sp_OACreate 'Microsoft.SqlServer.Management.Smo', objServer OUT
or
Microsoft.SqlServer.Management.Smo.Server
o
'Microsoft.SqlServer.Smo'
or
'SQLSMO.SQLServer'
January 16, 2012 at 12:53 pm
not sure there is a best practice
I personally have servers from sql2000 to sql2008r2
I tend to remote into them to use the tools on the servers
to make sure that...
December 21, 2011 at 1:13 pm
also there is an overhead with merge replication
if there are a large number of updates going both ways you will probably notice a performance hit
December 20, 2011 at 2:02 pm
also make sure none of the tables uses identiy columns
as you will have to program around these
December 19, 2011 at 1:53 pm
you could start with this
sp_configure 'remote query timeout (s)'
December 16, 2011 at 2:21 pm
that is how my backups work, I have each sqlserver backing up to 1 fileserver and the logs going to another fileserver. The tape then reads from those 2...
December 9, 2011 at 1:56 pm
usually when it is red either the copy or the restore jobs have had a problem.
usually you can tell which one by which report column is behind
look at the job...
December 9, 2011 at 1:49 pm
you said you ran the profiler
since it runs everyday it is probably a sql job or external job hitting the database, run the t_sql tuning option or t sql...
December 8, 2011 at 2:04 pm
not sure why you would want too
if the log isnt growing that big set it to 15 minutes
If you think is going to get that big set it 5 minutes
October 14, 2011 at 1:13 pm
Viewing 15 posts - 1 through 15 (of 213 total)