Viewing 15 posts - 19,846 through 19,860 (of 22,226 total)
IDENTITY columns do not duplicate, even without a constraint, when operating normally. You can force duplicates in by using IDENTITY_INSERT or by doing a RESEED, but the normal behavior 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
July 31, 2008 at 6:18 am
When you say duplicated, do you mean in the data? I've never seen that in normal functions, it must be a bug or you're not using the IDENTITY setting and...
"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
July 31, 2008 at 5:37 am
The newest version of Red Gate's SQL Prompt will do that for you and lots more. Also Red Gate's SQL Refactor has a way to clean up the layout 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
July 31, 2008 at 5:32 am
And just like your last post, take a look at the execution plans that will tell you a lot of what you need to know for making these sorts 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
July 31, 2008 at 5:30 am
Check the execution plan. WHERE clause order can affect some execution plans, but won't affect all. On a very simply query like this, it's unlikely to make a difference.
"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
July 31, 2008 at 5:28 am
dale_keller (7/30/2008)
"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
July 30, 2008 at 12:08 pm
gcopeland (7/30/2008)
"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
July 30, 2008 at 12:00 pm
I don't entirely understand the question...
You can insert into two tables:
INSERT INTO A
INSERT INTO B
But that's going to sequential, not simultaneous. In order to do them "at the same time"...
"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
July 30, 2008 at 10:32 am
From the first link:
So, I guess the only way round this is to disable the constraints - an option if your system is suffering from blocking or excessive reads caused...
"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
July 30, 2008 at 9:20 am
You don't need to create a diagram, but you can if you want to visualize what was created on the database. If you want to use the GUI to check...
"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
July 30, 2008 at 8:59 am
I thought it was fairly expected and common to put indexes on foreign keys (depending on needs of the queries used, etc., of course). I've never seen any documentation from...
"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
July 30, 2008 at 8:49 am
There's really not a difference between a query and a procedure. A procedure is just a query stored in the database. Queries can be parameterized just like queries. In fact,...
"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
July 30, 2008 at 7:54 am
Are the servers the same? Do they have the same amount of memory and the same size and number of processors? Like Gail already said, what do the execution plans...
"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
July 30, 2008 at 7:46 am
Good point on schemas. Although there, again, is a bunch of behavior that simply using it to group tables by function without also taking advantage of the security & execution...
"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
July 30, 2008 at 7:18 am
One thing to consider as well is that sprocs are vendor specific and require rewrites if you move from your current database platform, while there may be less changes if...
"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
July 30, 2008 at 7:02 am
Viewing 15 posts - 19,846 through 19,860 (of 22,226 total)