Viewing 15 posts - 46,111 through 46,125 (of 49,552 total)
Download the 180 day demo of SQL server if you don't have access to a SQL server and get familiar with management studio. The only way you're going to pass...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 24, 2008 at 12:13 am
Matt Miller (6/23/2008)
Gail - in 2005, if you knew it was going to recompile - would you FORCE the recompile on a given statement?
If I know absolutely, for...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 24, 2008 at 12:04 am
Add to that a full backup after switching back into full recovery mode. After truncating log you have no point-in-time recovery untill you take a full/diff backup.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 24, 2008 at 12:02 am
Manoj (6/23/2008)
That's perfact, I will do the same. If you can not able to do that then probably Last backup is the best one.
Actually the restore of last backup should...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 24, 2008 at 12:00 am
Depends. I've seen some cases where the slightly less accurate plan was better than a recompile of the entire proc (SQL 2000). On 2005 with statement level recompiles, would probably...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 10:35 am
Yup, though you can still get a stats-based recompile from the temp table, sometimes even more than once.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 10:19 am
The main advantage I've seen for table vars is that they don't cause a stored proc to recompile.
As for number of rows, it depends what you're going to do...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 9:51 am
Perhaps you could run profiler for a while and filter on the application name. I'm not sure 100% what appname reporting services uses, but it should be fairly easy to...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 9:42 am
SQL doesn't have an equivalent to the Oracle RowID.
What are you trying to achieve?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 9:02 am
And the process does exist? If you run sp_who2 <Spid> does ti return a row?
Are you sysadmin on that server?
Has the problem been around since the rebuild of the server...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 8:06 am
Depends why it's suspect. Check though the error log, see if you can find an entry in the log saying that SQL is marking the database suspect. It should give...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 6:42 am
Have you tried using the KILL command from query analyser?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 6:40 am
There's nothing useful in there. Look through your older logs, see if there's any entry related to msdb that doesn't simply say 'bypassing recovery because msdb is marked suspect'
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 6:11 am
mathewspsimon (6/23/2008)
considering all other thing are common for both cases,which do you think will be faster.
How long is a piece of string?
That's not a question that can be decisivly answered...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2008 at 4:56 am
Import into a staging table, do your clean up, move data to a proper table.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 22, 2008 at 11:55 pm
Viewing 15 posts - 46,111 through 46,125 (of 49,552 total)