Viewing 15 posts - 6,031 through 6,045 (of 7,187 total)
Dynamic SQL runs in its own scope, meaning that any variables, temp tables and so on will be lost. That is probably why it's asking you to declare the...
April 11, 2008 at 5:58 am
Is @ReportName the name of a column? If so, you can't use a variable to identify it. You'de either have to use dynamic SQL or change the design...
April 11, 2008 at 5:06 am
Marcin Wilczek (4/9/2008)
Now you say that once the DB is set to simple recovery the tran log should not grow as fast or at all?
This is oversimplifying it slightly, but...
April 10, 2008 at 1:56 am
Looks fine for what you're trying to do. But if I were you I wouldn't shrink the transaction log on a regular basis. Let it grow as large...
April 9, 2008 at 12:55 pm
Can we see the commands you're using at the moment, please?
Thanks
John
April 9, 2008 at 12:30 pm
ST
The main problem I have found in the past is that building the connection string is fiddly and unforgiving of the slightest error. Also, you may wish to consider...
April 8, 2008 at 1:37 am
Priya
That's a good start, but we still need sample data and expected results, please.
I think you might be struggling from what you've told me so far, though. If rows...
April 7, 2008 at 7:29 am
Paul
Does your Profiler trace show the settings that are being used when your application connects to the database (for example SET ANSI_NULLS ON and so on)? If so, put...
April 7, 2008 at 6:56 am
Priya
Before you worry about getting it to run faster, make sure it's correct. TOP doesn't mean anything without an ORDER BY clause, unless you're not worried which value is...
April 7, 2008 at 6:47 am
ST
Yes and yes. BOL is always the place to start when you're not sure of something. And you can schedule DTS packages using the dtsrun command line utility...
April 7, 2008 at 6:30 am
ST
I think using a DTS package would be simpler and possibly more robust.
John
April 7, 2008 at 6:25 am
Bill
Try this - doesn't need any IFs and does it in one line:
SET @end_date = COALESCE(@end_date, @start_date)
John
April 7, 2008 at 4:18 am
Nic
Yes, Task Manager isn't a reliable indicator of AWE memory. Try using the counters in Perfmon, or you should also find the same information in one of the dynamic...
April 3, 2008 at 8:20 am
Nic
I think with AWE you can't use dynamic memory, therefore you have to fix it at 4BG, say, and you should see it using that as soon as you've restarted...
April 3, 2008 at 8:11 am
You answered the question yourself. Set the /PAE switch in boot.ini and configure SQL Server to use AWE.
John
April 3, 2008 at 6:37 am
Viewing 15 posts - 6,031 through 6,045 (of 7,187 total)