Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    Good point! I'll update my query to not use LIKE and percent on state... as roughly less then one tenth of the database has "CA" for state. Thanks for the explanations regarding index... I am beginning to understand it better. I'll see if I can also add couple of other limiting items to be...
  2. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    Any thoughts on my last comment? Any particular data types for a column to be used for queries with "LIKE" comparison? I am still not sure what is the best index setup..been reading more on it and trying stuff, but still couldn't get the response under 5 seconds.
  3. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    George, Thanks! Those are really great ideas! The current search form gives a couple of options to search on: Keywords (one or more words, and using logic such as + means must have it and - meaning excluding it. Also from a drop-down selection to search All of the words, or Any of the words, or...
  4. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    Hi George, Thanks for the tips. I tried removing all but the primary and changed primary to clustered. Also added your suggested index. There wasn't much speed improvement. After login, it runs up to 10 seconds long, subsequent query soon after can be as quick as 6.125 seconds. The active and...
  5. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    index_name index_description index_keys IX_tblresumes nonclustered located on PRIMARY DateModified(-), DesiredOccupation, FullTime, PartTime, State PK_tblResumes nonclustered, unique, primary key located on PRIMARY ResumeEncID
  6. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    SELECT TOP 101 tblresumes.ResumeID, tblresumes.ResumeEncID, tblresumes.DesiredOccupation, tblresumes.City, tblresumes.State, tblresumes.DateAvailable, tblresumes.FirstName, tblresumes.LastName, tblresumes.Relocation, tblresumes.Skills, tblresumes.DesiredField, tblresumes.Polygraph...
  7. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    Anyone with ideas/tips or help on efficient indexing?
  8. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    BTW, on SQL 2000 and 2008. I took from an older server with SQL 2000 the database, detached and simply just attached at the new location. Fixed user accounts and that's it.
  9. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    Please forgive me for not being very knowledgeable on SQL. I wasn't sure how to reindex, so I looke dit up and followed method 1 from this link: Reindex methods Since I still didn't see any improvement, and my script was still timing out, I looked around and changed the database's compatibility...
  10. POSAPAY

    SQL 2008 express - slower query than on SQL 2000

    I've got a Classic ASP vbscript application that I'm testing on two new Windows 2008 R2 servers, with one running SQL 2000, and the other running SQL 2008 express The SQL 2000 seems to run it just fine. But the SQL 2008 express times out. I set in the script the query timeout to be 0...
  11. POSAPAY

    run 32 bit dll on win 2008 r2 64bit and called from IIS from a webpage is not working

    Got it solved.. I've found a 64bit version of the dll file, and put it in system32\inetsrv and it works now.
  12. POSAPAY

    run 32 bit dll on win 2008 r2 64bit and called from IIS from a webpage is not working

    yes.. that is where I put the file and that was the directory I was in from cmd and tried regsvr32
  13. POSAPAY

    run 32 bit dll on win 2008 r2 64bit and called from IIS from a webpage is not working

    I've been battling this issue for a few days now... I am relatively new to Win2008 r2 and also new to 64 bit. Got a credit card processing encryption tool of dll and exe file that my website must call. I believe the dll file is 32 bit...so I've put it in the SysWOW64 folder. (on an older box it...
  14. POSAPAY

    Login timeout expired on Win2008R2 and MS SQL 2000 - and using Classic ASP

    okay. never mind the question.. just solved it. I installed SQL 2000 SP4 and it resolved my issue.
  15. POSAPAY

    Login timeout expired on Win2008R2 and MS SQL 2000 - and using Classic ASP

    BTW, I just tried from Administrative Tools > ODBC Sources to add a System DSN, and got the same error. I was trying to connect by TCP/IP. and using the server's network name instead of IP. With IP it wouldn't even go that far. SQLState: HYT00 SQL Server Error: 0 ...Login timeout expired Any...
  16. POSAPAY

    Login timeout expired on Win2008R2 and MS SQL 2000 - and using Classic ASP

    I have moved a Classic ASP application to a new Windows 2008 R2 server, and installed MS SQL 2000 for it. All went well until I tried to run the first page of the website, where it says: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver]Login...
  17. POSAPAY

    Distinct rows based on one column, yet get the other columns

    MarkSweetland - thanks for your quick reply. Sample data would be: Table: tblReklamLog Fields: ID, ReklamKod, UserIP, UserDomain, LinkSource, DateCreated Data: 1, AUW1GMZU, 200.200.200.200, dsl123.somedomain.com, http://google.com/search?hl=etc, 12/1/2011 5:30:09 AM 2, AUW1GMZU...
  18. POSAPAY

    Distinct rows based on one column, yet get the other columns

    I'm trying to display from a log table records that have unique counter fields and date, and often the same IP address creates multiple entries, but I'd only want one record per IP address, and have all of it sorted by the date created. here is what I have now, but it is still not listing...
  19. POSAPAY

    SP selecting a date range to be fine-tuned to the hour

    My SP runs once an hour by a SQL job is selecting from the database a number of records that have a field with a date that is not older than 5 days, yet older by a variable passed in. The problem is, my logic only names it by DAY, and not fine-tuned to the HOUR at least. WHERE Active = 'T' AND...

Part and Inventory Search

Back
Top