Viewing 15 posts - 20,776 through 20,790 (of 22,224 total)
You can use the SQL Server Management Studio to connect to and work with Compact databases though, if that helps. It's not stored procedures but it is a bit easier...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 28, 2008 at 6:10 am
Version 8.0 is actually "SQL Server 2000."
It sounds like security has changed inside your database? Possibly.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 12:50 pm
What error? Are you running in SQL Server 2008? This is a 2008 forum.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 12:40 pm
Looks like tempdb ran out of space.
Either you ran a query against such a large amount of data that you maxed out your tempdb or you may have something wrong...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 12:28 pm
Also it could be the statistics are changing in your data. Make sure that they're up to date. It's really important, as noted above, to look at the execution plan,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 11:46 am
Database design theory, I'll leave to someone else. I'm using an ancient text called "Handbook of Relational Database Design" by Fleming & von Halle. It's too basic for most of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 11:40 am
Oops. Missed that one. I hate when I get hung on the first error I see.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 7:29 am
How about
OUTPUT INSERTED.CategoryId
because there wasn't a column in the list called ID
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 7:05 am
I don't think that's possible. Unless there's a way to make the Compact database a linked server, there's no way to open a connection within TSQL. You could write CLR...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 6:58 am
I agree that NOT using a cursor is an even better approach.
However, to answer your question, I wouldn't use the WHILE loop with a BREAK statement because it's really a...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 6:23 am
It sure sounds like you need to set up Profiler. That will capture the stored procedure calls along with the parameters passed, no extra code on your part required. You...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 6:19 am
A teenager down at the dojo says I'm losing my touch... He's testing in August. I'll "touch" him then.
Anyway, glad to be of use. One other point worth mentioning is...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 27, 2008 at 5:33 am
Not even, don't worry about it.
You've got a lot of options. You mentioned triggers. That is one possibility. Another would be to use the OUTPUT clause from your data modification...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 26, 2008 at 11:23 am
See the post above by Julius. That shows how to unpack the XML files.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 26, 2008 at 10:28 am
Can you edit the sample XML to remove the angled brackets? I usually use square brackets and comment the code. The angled brackets results in blank data as you see...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 26, 2008 at 6:38 am
Viewing 15 posts - 20,776 through 20,790 (of 22,224 total)