Viewing 15 posts - 1,831 through 1,845 (of 2,496 total)
The very minimum build you should consider is SP2 plus Cumulative Update 1. (See KB935356 re CU1). Although SP2 fixed a large number of problems it introduced some...
January 10, 2008 at 4:28 am
The maximum distance between geographically dispersed nodes has gone up over time as technology has improved. This relates both to the software involved in dealing with the heartbeat and...
January 9, 2008 at 4:14 am
HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name\MSSQLServer\LoginMode
The INSTANCE NAME value is wrong for SQL Server 2005 instances. You will need to use MSSQL.n, where n relates to the instance you...
January 9, 2008 at 3:56 am
Your developer says it is quicker to create specific tables in tempdb rather than using #tables?
What process was used to test this? It is amazing how different response time...
January 9, 2008 at 3:41 am
If your tempdb has grown to 15 GB, then something must have run that needs that space. The only question is if it was a one-off process.
If you can...
January 9, 2008 at 3:02 am
Congratulations!!! Well overdue but at least it has happened.
January 4, 2008 at 2:43 am
All of the 'big 4' RDBMS products are fit for purpose, and all will do what most businesses need to be done. The best one to use is the...
January 3, 2008 at 2:45 am
Aye, but you can use OPTION (MAXRECURSION 0) to allow unlimited recursion, and get billions of rows in the result set if you need them.
January 2, 2008 at 6:57 am
Use a recursive CTE to do this, it is far more elegant than multiple cross joins.
Graeme Birchall has superb examples of generating test data using recursive CTEs in his DB2...
January 2, 2008 at 5:01 am
In order to plan a backup strategy you need to know the recovery SLAs. If there are none, then make them and get them approved.
If your business customers have...
January 2, 2008 at 4:56 am
A Global Temp Table is only global to the SQL Server instance it is created on, not to the entire globe.
It is called a Global Temp Table because it is...
January 2, 2008 at 4:45 am
Try putting the 32-bit DLLs into the Windows sysWOW folder. When I needed to use some custom 32-bit OCX components in DTS packages I was installing on 64-bit SQL...
December 31, 2007 at 6:04 am
I have found that if the DLL is in the default folder (e.g. c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn) then running sp_addextendedproc without specifying the full path of the DLL works OK....
December 31, 2007 at 5:32 am
I have not checked this myself, but one possibility for using named columns instead of SELECT * could be included columns in an index.
I agree that SELECT * FROM table...
December 31, 2007 at 4:02 am
Viewing 15 posts - 1,831 through 1,845 (of 2,496 total)