Viewing 15 posts - 47,356 through 47,370 (of 49,552 total)
We're not that strict here. The same post in 2 different places means that people will waste time answering something that has been answered already.
If you realise the post is...
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
February 14, 2008 at 9:02 am
Not at all. SQL's quite capable of handling index creation while the DB's in use.
Since you're on SQL 2005, you can create the index either online or offline. Offline is...
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
February 14, 2008 at 8:52 am
Please don't cross post. It just wastes people's time.
Answered on the following thread - http://www.sqlservercentral.com/Forums/Topic455740-169-1.aspx
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
February 14, 2008 at 8:50 am
Triggers returning rowsets is frowned upon. There's a server setting that prohibits triggers from retruning result sets at all.
I would suggest you stick to print.
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
February 14, 2008 at 8:46 am
It's a x64 server, so no PAE memory, but 14GB is still a little too high. I prefer my available memory to be at least 1.5-2GB on servers with 16GB...
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
February 14, 2008 at 8:43 am
Why do you want to lock the tables?
iirc, in SQL 2000, creating a nonclustered index makes the table readonly for the duration of the index creation
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
February 14, 2008 at 8:39 am
Frank Woodard (2/14/2008)
select * from table where [datetime] between '2007/02/14' and '2007/02/15' this will give you 2007/02/14 from 00:00:00.0 through 23:59:59.9
That will return 2007/02/14 from 00:00:00.000 through 23:59:59.997 and...
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
February 14, 2008 at 8:35 am
Probably both have select locks on a page and both want to escalate to exclusive. Instant deadlock.
Could you post the code for both the proc and the trigger, as well...
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
February 14, 2008 at 8:13 am
Steve Jones - Editor (2/14/2008)
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
February 14, 2008 at 8:08 am
Stu (2/14/2008)
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
February 14, 2008 at 3:51 am
No idea, sorry.
If you just do a straight Select 1 FROM a, do you get the same error?
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
February 14, 2008 at 1:18 am
The thing is, you can't create a variable of type image. If it were SQL 2005, you could use varbinar(max) but that's not an option on 2000. So the suggested...
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
February 14, 2008 at 12:19 am
Can you post the import proc please?
There are serveral people here very good at 'fixing' cursors (by replacing them with set-based code)
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
February 13, 2008 at 10:16 pm
The do work together pretty well.
Make sure when you install 2005 that you create a new instance and don't upgrade the 2000 instance.
I would recommend setting the max memory...
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
February 13, 2008 at 9:58 pm
Absolutely. While it wouldn't speed up the entire process, it would shorten the length of the locks on the updated 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
February 13, 2008 at 9:55 pm
Viewing 15 posts - 47,356 through 47,370 (of 49,552 total)