Search results for query: *

And the solution from SQL Magazine: When using SEM to display the rows from a table, all rows are returned by a "firehose cursor"; however, only the rows that are displayed have been processed. A "firehose cursor" refers to how the server sends rows to the client as fast as...

From MSDN: Some providers, such as SQL Server, implement a forward-scrolling, read-only (or 'firehose') cursor mode, meaning that they can efficiently retrieve data by keeping a connection open. When working with such providers, the connection could be blocked by another user's transaction...

Nothing to worry about - this just when Enterprise Manager or SQL Service Manager routinely polls the SQL Server to determine whether it (as well as SQL Server Agent, MSDTC, and Full-Text Search) is still running.

Our DBA (based at the same physical location as the box) ran the same query via a PCAnywhere connection, and it still took over 3½ minutes.... This is a new server - any DBA's out there have ideas about what setting may need 'tweaking'? I don't have sa rights, so can't get to most...

Could this be a network issue as opposed to a SQL performance issue? I ask because I did some more poking around, and the same SELECT * on my old (local) Prod server returned about the same rowcount in 45 seconds. We recently migrated our live db to a centralized server shop that is remote -...

Why not just have one field [Login Timestamp] and separate in code as required - I do it all the time, and works fine.

Okay, here's my problem. I have a massivley complicated query, that creates and populates two temp tables, then unions them - I want the output. This is the easy bit - it takes about three minutes to crunch all this lot. The problem arises when I either: SELECT * FROM #Temp1 UNION ALL...