Viewing 15 posts - 1,006 through 1,020 (of 1,271 total)
Yes, it matters where you put it. I generally put it first.
November 22, 2006 at 10:26 pm
Nah, the performance will be the same with either one of them.
November 22, 2006 at 10:05 pm
Is there any part of that process that can not be done entirely within a single stored procedure? I believe that it could be.
November 21, 2006 at 3:11 pm
It is very good performance wise. Much better than returning the entire row.
November 21, 2006 at 2:15 pm
That doesn't complicate it much at all. I could actually do it in 2 steps without disabling the foreign key, but the update query would be overly complex, and I...
November 21, 2006 at 1:50 pm
When SQL Server converts a date stored as a string without a time value to a datetime, it assumes the time to be 00:00:00.000 AM. So even if you do...
November 21, 2006 at 1:34 pm
Wow, such complex solutions!!
It is a simple process. The 4 steps are:
Alter Table RespondentLOV...
November 21, 2006 at 1:23 pm
If you are going to be doing this on a regular basis, create a Linked Server to use.
November 21, 2006 at 1:01 pm
Did you upgrade the SQL client tools on the client side as well? They all have to be upgraded together.
November 21, 2006 at 12:59 pm
Use sp_helptext. The text column in syscomments is nvarchar(4000) and stored procedures can be up to 128 MB in size. If the procedure is longer than 4000 characters, the output...
November 21, 2006 at 12:55 pm
Does the table have a column to track update times? If so, you can simply query the table for anything with an update time newer than the last time you...
November 21, 2006 at 12:27 pm
This information is stored in the registry so you have to manipulate teh registry to do this. That's not something I would recommend to anyone unless they really know what...
November 21, 2006 at 12:15 pm
Native mode refers tot he way that SQL Server interacts with external databases. SQL Server Native mode means that it is using a language that only SQL Server understands. For...
November 21, 2006 at 12:13 pm
It sounds to me like locking is the most likely cause. Some query or process had row # 32753 locked in a transaction. If you select just the first 32752...
November 21, 2006 at 11:57 am
You can use DBCC FlushProcInDB to fee the proc cache within a single database. There are a couple of good articles on SQL-Server-Performance.com that you should read:
November 21, 2006 at 11:49 am
Viewing 15 posts - 1,006 through 1,020 (of 1,271 total)