Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8842537
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T10:59:01+00:00 2026-06-14T10:59:01+00:00

I have an EF context using linq that is being executed on multiple sql

  • 0

I have an EF context using linq that is being executed on multiple sql servers of varying types. What I have found is that linq is causing a syntax error on a sql server 2000 box because the linq translation for .FirstOrDefault() is being translated into sql that uses SELECT TOP (1) instead of SELECT TOP 1 and it would seem that the parenthesis are causing this syntax error as they are not supported in this context in sql server 2000.

Is it possible to force linq to use SELECT TOP 1 instead of SELECT TOP (1) ?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T10:59:02+00:00Added an answer on June 14, 2026 at 10:59 am

    you can use ToList().Take(1) method after ordering.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a record that came from the follow linq query: using (var context
I'm accessing a data context object that is auto-generated by using LINQ to SQL.
I have generated few classes using to LINQ to SQL one of them being
We are using Linq To SQL with our own data context logic that executes
We are using Linq To SQL with our own data context logic that executes
Given this LINQ to SQL: using (var db = Database.Context) { var root =
I have been looking at making the switch from SQL TableAdapters to Linq using
I wrote a tool that queries/updates a database using Linq to SQL. The entity
I have been having some issues with LINQ-To-SQL around memory usage. I'm using it
I have a repository implemented using LINQ to SQL. I need to do Unit

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.