Viewing 15 posts - 3,181 through 3,195 (of 6,036 total)
Stored procedure may return results via output parameters, output parameters+recordset, multiple recordsets, temp table(s), etc.
Metadata for which of these options you want to find?
_____________
Code for TallyGenerator
January 15, 2008 at 1:47 pm
goodguy (1/15/2008)Pardon me for nitpicking, if the alias 't' is assigned in the outer query, how can it be recognised inside the inner query?
All aliases assigned in outer queries, are...
_____________
Code for TallyGenerator
January 15, 2008 at 2:47 am
CREATE TABLE ResultSetYeildingProc (...)
INSERT INTO ResultSetYeildingProc
exec usp_myResultSetYeildingProc
SELECT * FROM ResultSetYeildingProc
_____________
Code for TallyGenerator
January 14, 2008 at 8:10 pm
I believe error explains itself.
2 or more ID's have the same description.
Run
[Code]select COUNT(id), description
from tblProgram
GROUP BY description
HAVING COUNT(id) > 1[/Code]
and see which description(s) is an offender.
P.S. You should...
_____________
Code for TallyGenerator
January 14, 2008 at 7:43 pm
IF @@ROWCOUNT > 10 -- assume that normal query to affect not more than 10 rows
ROLLBACK
ELSE
COMMIT
_____________
Code for TallyGenerator
January 14, 2008 at 5:59 pm
For this kind of files it's better to use ODBC drivers.
They read those strings with identifiers properly.
I created text file TestInsert.txt in the folder C:\TextFiles (local to the SQL Server...
_____________
Code for TallyGenerator
January 14, 2008 at 3:58 pm
It's acceptable if number of rows never gonna exceed 1000.
Then it's gonna be another topic in "Performance" forum.
If you really cannot trim the ID's on insert (did you think about...
_____________
Code for TallyGenerator
January 14, 2008 at 2:29 pm
All of you are wrong.
Using "," as delimites is an error waiting to happen.
mdjtlj, ask you supplier to build a test file containing '19" Monitor'.
Then try to process that file.
_____________
Code for TallyGenerator
January 14, 2008 at 2:22 pm
You need to pinpoint the row(s) for UPDATE.
I guess your conditions in WHERE clause are such they cause table/index scan and lock all scanned records.
1st thing you need to try...
_____________
Code for TallyGenerator
January 13, 2008 at 1:51 pm
SQL Server is not a text editor.
It's Relational Database Management System.
You have to choose:
- either to store you data in proper relational database and use RDMS to manage it;
- or...
_____________
Code for TallyGenerator
January 12, 2008 at 5:07 am
Schedule a job for the next second.
Job must be created earlier. Trigger just should schedule it for one-off execution as GETDATE() + 1s.
_____________
Code for TallyGenerator
January 11, 2008 at 4:32 am
How do you know that?
I use to think.
The 4581 ms is in the Query Analyzer.
QA is a front end application.
The only difference essential (in our...
_____________
Code for TallyGenerator
January 11, 2008 at 4:16 am
So, it gives you the answer:
All the time is spent on uploading data to front end.
There is nothing to improve in SQL Server performance.
Improve your upload channel.
Or don't store blobs...
_____________
Code for TallyGenerator
January 10, 2008 at 9:57 pm
Because it takes about a minute to execute that query you may add BatchStarted event in your trace and try to catch its SPID in master..sysprocesses while it's being executed.
No...
_____________
Code for TallyGenerator
January 10, 2008 at 6:59 pm
How long does it take to execute the version of query I posted?
_____________
Code for TallyGenerator
January 10, 2008 at 6:04 pm
Viewing 15 posts - 3,181 through 3,195 (of 6,036 total)