Viewing 15 posts - 5,011 through 5,025 (of 6,486 total)
Re-read the previous post (edited) - I forgot you were doing this all in a report, and that reports prefer one single select statement with parameters....
January 28, 2008 at 9:26 am
First - you're right to pursue putting the answers in one single table. So keep following that data structure along - you're on the right track there.
As to gettting...
January 28, 2008 at 9:23 am
Then you're using it in a report? Reports do the declaring - just "off the screen". Look under parameters - you'll see them declared.
The point is -...
January 28, 2008 at 8:40 am
GilaMonster (1/28/2008)
You're aiming for having the log file a steady size, not needing to grow.
Agreed - and when you find this stable place - don't shrink the log file anymore....
January 28, 2008 at 8:36 am
The variables need to be declared somewhere. The code I gave you would need to be inserted into your existing process (which apparently had already handled the declaration/passing of...
January 28, 2008 at 8:27 am
Piotr Rodak (1/28/2008)
January 28, 2008 at 8:21 am
Again - Count(*) is overkill for a scenario like that. You don't care how many there are, you just want to know there are some matching records.
So instead of
select...
January 28, 2008 at 8:08 am
Also - just exactly how big is your database? 156GB on a log file seems extreme, unless you're dealing with a database with rather special needs...
January 28, 2008 at 7:57 am
A few smallish things:
1.Keep in mind that the RESEED will not automatically reseed to a SMALLER number, but it will find the appropriate next HIGHER identity value to put it...
January 28, 2008 at 7:53 am
If you simply want to know about existence, you probably want to look at using something like an EXISTS clause, possibly combining it with a TOP 1 clause.
Count(*)...
January 28, 2008 at 7:32 am
Project Plan? You mean there's a PLAN? hehe....
It's a definite challenge. You have to have a vision of where you're heading, but let's face it - there's...
January 28, 2008 at 7:26 am
Assuming you store the duration (flight time) as a datetime as well, then
cast(cast(duration as decimal(18,4))*24 as int) --this would return your hours
datediff(day,0,duration)*24+datepart(hour,duration) -- method #2 for returning hours
datepart(minute,duration) --...
January 27, 2008 at 12:45 pm
There's no reason to be doing all of this. SQL datetime fields CAN be edited in Access, nevermind the formatting that's applied to it. They're stored in a...
January 27, 2008 at 9:47 am
Cool! I will have to see if I can run the next "big one" I get this way to get a feel, but it sounds like performance has definitely been...
January 27, 2008 at 9:21 am
That's a MAPI login failure, which happens often enough when SQLMAil isn't configured correctly, and/or the service accounts (the user names starting up SQL Server and/or SQL Agent) can't access...
January 27, 2008 at 8:54 am
Viewing 15 posts - 5,011 through 5,025 (of 6,486 total)