Viewing 15 posts - 256 through 270 (of 921 total)
It's a phased retirement; explained here:
http://www.microsoft.com/ntserver/ProductInfo/Availability/Retiring.asp
January 13, 2004 at 7:50 am
Revising Frank's solution for the OP's data types:
declare @myyear char, @mydays char(3)
set @myyear = '3'
set @mydays = '057'
select dateadd(d,@mydays-1,'200' + @myyear)
January 12, 2004 at 3:27 pm
That's exactly backwards advice. Putting the column values in a function makes the predicate non-sargable. Even just converting the values (as your solution also...
January 12, 2004 at 7:20 am
Terry-
Those symptoms sound consistent with enabling AWE but not having the /pae parameter correctly entered in the boot.ini file.
January 9, 2004 at 11:45 am
Terry--
Okay, then.
Did the SQL Server service login account have the Lock pages in memory privilege?
Did you set awe enabled to 1 in the SQL Server configuration?
Are you using multiple...
January 9, 2004 at 10:53 am
You must use Windows 2000 Advanced Server or Datacenter Server, or Windows Server 2003 Enterprise Edition or Datacenter Edition.
January 9, 2004 at 9:42 am
How about just:
CREATE PROCEDURE dbo.spProductMaxDetailsGet
AS
SELECT TOP 1 WITH TIES *
January 9, 2004 at 9:35 am
Terry--
What versions and editions of SQL Server and Windows Server?
January 9, 2004 at 9:25 am
No; that's only when using AWE memory, i.e. memory greater than 4GB by using the /PAE option.
January 9, 2004 at 8:04 am
WHERE LastDate = CONVERT(char(10),GETDATE(),111)
Why use varchar(10) for dates instead of one of the temporal data types?
January 9, 2004 at 7:36 am
That's 1,048,516 Terabytes, not 1.05 Terabytes. For each database. Instances have no bearing on this limitation.
January 9, 2004 at 7:32 am
1,048,516TB for SQL Server 7 or SQL Server 2000, unless you're using MSDE where it's limited to 2GB. No difference when using instances.
January 9, 2004 at 6:55 am
I can't restart a server with 4GB right now to verify this, but I believe that using just -g will be the same as not using the switch. You will instead...
January 9, 2004 at 6:49 am
That's normal. SQL Server 2000 will not reserve the last 384M for its memory pool. It still uses memory outside its pool for processes like extended stored procedures, distributed queries, and tran log...
January 9, 2004 at 5:47 am
Viewing 15 posts - 256 through 270 (of 921 total)