Asim

Have you tried

GROUP BY YEAR(LossDate)

and

GROUP BY MONTH(From_Date)?

John

OK - if you want the operating system only to use 1GB of RAM (instead of the default of 2GB), which I presume you do since you've set SQL Server...

Harris

I imagine that if you include the characters "password" in your password, then the setup program will construe that as not being a strong password.

John

Pivoting data in SQL Server 2000 can be done, but it's clumsy and cumbsersome.  Search this site - there are plenty of answers to this sort of problem.

What I'd do...

I suspect this might be to do with SET QUOTED IDENTIFIER.  Have a look at that topic in Books Online, then try altering your procedure so as to remove the...

Please post your query, some DDL, sample data and expected results.  It's much easier for us to solve if you do that than it is if we have to try...

Do you have the /3GB and /PAE switches in your boot.ini file?  Is your reporting server a dedicated SQL Server, or does it also do anything else?

John

Before you use locking hints or change the transaction isolation level, make sure you understand the implications of what you are doing.

Another road you may want to go down is...

I think I'm right in saying that this was true in SQL Server 7.0, but not 2000.  You can now use Enterprise Manager or the SQL Server Service Manager to...

Jeff

The dtsrun command is what you need for the first point.  It's a command-line utility so you don't need to call it from a stored procedure - you can use...

George

You can use the OPENROWSET function to run a query against the Excel sheet, and then dump the results in the temp table.  The syntax for using the Jet OLE...

Michael

You use the Jet OLE DB driver.  See the topic "OLE DB Provider for Jet" in Books Online.

John

OPENROWSET is indeed what I meant.  You're right, the syntax is messy, and that's why it's best to use linked servers if you have sufficient access to add one.  From...

I'm sure the 16GB /3GB issue is documented in lots of other places, but this is the first one I found:

http://www.sql-server-performance.com/awe_memory.asp

John

Hemant

Happy to help.  As for table variables, they do have a slightly different behaviour on the surface, but underneath they do the same thing: they are created in memory but moved...