Viewing 15 posts - 91 through 105 (of 457 total)
Original post taken down, a good point was made in the other thread.
August 10, 2007 at 3:16 pm
The problem is that Microsoft has not released a 64-bit MDAC which includes the Jet database engine. It makes 64-bit reading of Excel or MS Access data sources in...
August 9, 2007 at 12:30 pm
As usual, I find myself agreeing with Ninja.
August 9, 2007 at 10:05 am
I've worked for companies which finalized the database structure before a line of code was written and companies where the database structure was more of a fluid thing throughout the...
August 9, 2007 at 10:04 am
You can drop the primary key, however this would likely cause a lot more problems. Most of the time primary keys are placed for a good reason (i.e. to...
August 8, 2007 at 2:02 pm
There are some third party tools which can help you view the actions in the transaction logs. Lumigent's Log Explorer is one such product. I have no direct...
August 7, 2007 at 9:55 pm
Yeah, I had that thought but it's late in the day and I'd like to think I got at least one person helped today (too bad it's not one person...
August 7, 2007 at 6:49 pm
I'd still strongly advise against it, I haven't found the case where IN was a better move than a join (PIVOT and UNPIVOT not withstanding). But here it is...
August 7, 2007 at 6:12 pm
My advice: Don't.
Use an inner join. SQL Server 2005 always tries to convert IN to a join whenever possible, however sometimes it can't. The reason being is that...
August 7, 2007 at 5:59 pm
You might try testing rebuilding a few indexes to see what the log utilization is for varying sizes of indexes first. I'm sure it's not going to be the...
August 7, 2007 at 10:03 am
There's not any real good way to predict the log space needed.
It's worth noting that if you're in the full recovery mode, rebuilding indexes takes a lot of log space,...
August 7, 2007 at 9:36 am
I usually have a standard error handler that looks something like this (simplified):
BEGIN TRANSACTION
INSERT mytable (val1, val2)
VALUES (@val1, @val2)
SELECT @err = @@ERROR
IF @err 0
BEGIN
SET @err_string = 'Insert...
August 6, 2007 at 10:48 am
It's hard to say without knowing more about your problem, but one solution might be to use a view which UNION ALLs together the result sets from your tables... ...
August 6, 2007 at 8:08 am
A login is a principal at the server level and can be granted/revoked/denied permissions at the server level.
A user is a principal at the database level and can be granted/revoked/denied...
August 3, 2007 at 9:59 am
Viewing 15 posts - 91 through 105 (of 457 total)