Viewing 15 posts - 2,971 through 2,985 (of 3,606 total)
Kenneth, try using BETWEEN on a column with a clustered index and then comparing the > and < method.
October 12, 2004 at 3:35 am
If your SELECT involves a single table then you should be able to Add.
Make sure that whatever user you are connecting to the database has read/write access.
Your best bet is...
October 12, 2004 at 3:32 am
When it comes to WHERE clauses I have found that the different comparison operators have different performances. In order of speed (fastest first)
If you can...
October 12, 2004 at 2:45 am
Theoretically you could simply run the Access upsizing wizard http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part2/c0561.mspx
I would start by reading up about the different datatypes in SQL Server and mapping them to the various MS...
October 12, 2004 at 1:48 am
When the proc is called from your application open up SQL Query Analyser and run sp_lock and sp_who to see what is going on.
Within Enterprise Manager have a look at...
October 11, 2004 at 3:25 am
If your users are administrator then you have big problems.
If you want to block Access and Excel usage then what rights should they legitimately hold?
What logon are they using? Why...
October 11, 2004 at 2:18 am
If this procedure has been working fine with good performance then my first suspicion would be that something else is causing the problem. Perhaps some long running process that is...
October 11, 2004 at 2:14 am
I've heard of modelling tools, but then I've heard of unicorns and phoenixes as well
To me Key = Index.
October 8, 2004 at 9:10 am
AK1 needs to be a unique key if you are going to do this, otherwise you will take an AK47 to your data integrity.
As...
October 8, 2004 at 8:38 am
Note POWER will give an arithmetic error if you exceed 31 issues because POWER can only return a 32 bit integer.
October 7, 2004 at 8:55 am
DECLARE @tbl TABLE(Id Int , Issue CHAR(8))
DECLARE @byLoop TinyInt
SET @byLoop=1
WHILE @byLoop<32
BEGIN
INSERT @tbl(Id , Issue)
SELECT POWER(2,@byLoop-1),'Issue ' + CAST(@byLoop AS VARCHAR(2))
SET @byLoop=@byLoop+1
END
SELECT * from @tbl
October 7, 2004 at 8:52 am
This design limits the number of possible values to:
If you are happy with that then why not prepopulate...
October 7, 2004 at 8:10 am
Personally I would have three tables.
If you haven't already done so I would create an integer field to act as the primary key for the Customers and Models table.
On the...
October 7, 2004 at 1:25 am
I am assuming here that you have performed some form of large delete operation and want to shrink your database file?
Firstly, do a DBCC DBREINDEX on that tables from which...
October 6, 2004 at 1:47 am
In what way Jamie, what were you looking for?
October 6, 2004 at 1:39 am
Viewing 15 posts - 2,971 through 2,985 (of 3,606 total)