Is “SET IDENTITY_INSERT” required to insert arbitrary GUID into [uniqueidentifier] column?
SQL Server 2016 and 2017, Standard Edition
I need to insert raw data (from another table) into a table that has two uniqueidentifier columns.
Does this require that I use SET IDENTITY_INSERT Carrier ON?
Here is the table:
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
CREATE TABLE [dbo].[Parkingspace](
[ParkingspaceId] [uniqueidentifier] NOT NULL,
[AccountId] [uniqueidentifier] NULL,
[ParkingspaceType] [smallint] NULL,
CONSTRAINT [PK_ParkingspaceId] PRIMARY KEY CLUSTERED
(
[ParkingspaceId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY]
) ON [PRIMARY]
Will the following work without the IDENTITY_INSERT option? (I think it should but the DBA here is very married to the IDENTITY_INSERT option.)
INSERT INTO Parkingspace
(ParkingspaceID,AcountID,ParkingspaceType)
SELECT * FROM PRODDBCopy.Parkingspace
sql-server sql-server-2016 sql-server-2017 identity uniqueidentifier
edited 8 hours ago
Paul White♦
52k14278450
asked 8 hours ago
samsmithsamsmith
1,53321942
add a comment |
SQL Server 2016 and 2017, Standard Edition
I need to insert raw data (from another table) into a table that has two uniqueidentifier columns.
Does this require that I use SET IDENTITY_INSERT Carrier ON?
Here is the table:
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
CREATE TABLE [dbo].[Parkingspace](
[ParkingspaceId] [uniqueidentifier] NOT NULL,
[AccountId] [uniqueidentifier] NULL,
[ParkingspaceType] [smallint] NULL,
CONSTRAINT [PK_ParkingspaceId] PRIMARY KEY CLUSTERED
(
[ParkingspaceId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY]
) ON [PRIMARY]
Will the following work without the IDENTITY_INSERT option? (I think it should but the DBA here is very married to the IDENTITY_INSERT option.)
INSERT INTO Parkingspace
(ParkingspaceID,AcountID,ParkingspaceType)
SELECT * FROM PRODDBCopy.Parkingspace
sql-server sql-server-2016 sql-server-2017 identity uniqueidentifier
edited 8 hours ago
Paul White♦
52k14278450
asked 8 hours ago
samsmithsamsmith
1,53321942
add a comment |
SQL Server 2016 and 2017, Standard Edition
I need to insert raw data (from another table) into a table that has two uniqueidentifier columns.
Does this require that I use SET IDENTITY_INSERT Carrier ON?
Here is the table:
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
CREATE TABLE [dbo].[Parkingspace](
[ParkingspaceId] [uniqueidentifier] NOT NULL,
[AccountId] [uniqueidentifier] NULL,
[ParkingspaceType] [smallint] NULL,
CONSTRAINT [PK_ParkingspaceId] PRIMARY KEY CLUSTERED
(
[ParkingspaceId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY]
) ON [PRIMARY]
Will the following work without the IDENTITY_INSERT option? (I think it should but the DBA here is very married to the IDENTITY_INSERT option.)
INSERT INTO Parkingspace
(ParkingspaceID,AcountID,ParkingspaceType)
SELECT * FROM PRODDBCopy.Parkingspace
sql-server sql-server-2016 sql-server-2017 identity uniqueidentifier
edited 8 hours ago
Paul White♦
52k14278450
asked 8 hours ago
samsmithsamsmith
1,53321942
SQL Server 2016 and 2017, Standard Edition
I need to insert raw data (from another table) into a table that has two uniqueidentifier columns.
Does this require that I use SET IDENTITY_INSERT Carrier ON?
Here is the table:
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
CREATE TABLE [dbo].[Parkingspace](
[ParkingspaceId] [uniqueidentifier] NOT NULL,
[AccountId] [uniqueidentifier] NULL,
[ParkingspaceType] [smallint] NULL,
CONSTRAINT [PK_ParkingspaceId] PRIMARY KEY CLUSTERED
(
[ParkingspaceId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY]
) ON [PRIMARY]
Will the following work without the IDENTITY_INSERT option? (I think it should but the DBA here is very married to the IDENTITY_INSERT option.)
INSERT INTO Parkingspace
(ParkingspaceID,AcountID,ParkingspaceType)
SELECT * FROM PRODDBCopy.Parkingspace
sql-server sql-server-2016 sql-server-2017 identity uniqueidentifier
sql-server sql-server-2016 sql-server-2017 identity uniqueidentifier
edited 8 hours ago
Paul White♦
52k14278450
asked 8 hours ago
samsmithsamsmith
1,53321942
edited 8 hours ago
Paul White♦
52k14278450
asked 8 hours ago
samsmithsamsmith
1,53321942
edited 8 hours ago
Paul White♦
52k14278450
edited 8 hours ago
Paul White♦
52k14278450
edited 8 hours ago
Paul White♦
52k14278450
52k14278450
asked 8 hours ago
samsmithsamsmith
1,53321942
asked 8 hours ago
samsmithsamsmith
1,53321942
asked 8 hours ago
samsmithsamsmith
1,53321942
1,53321942
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
IDENTITY_INSERT is only used for columns with the IDENTITY property.
UNIQUEIDENTIFIER is merely a data type.
Your insert statement will work.
answered 8 hours ago
Paul White♦Paul White
52k14278450
Thank you. That is what I also understood. I found it odd that the DBA gave me "SET IDENTITY_INSERT Carrier ON" all over tables that lack the Identity attribute.
– samsmith
8 hours ago
1
@samsmith DBAs can be odd, just like everyone else 😃
– Paul White♦
8 hours ago
I know. It is cool. I know this is not harmful. But if the folks using the SQL from the DBA actually insist on understanding what they are doing (as I do), they will look this stuff up. And when the docs indicate that the DBA is giving superfluous stuff, it opens a can of worms like.... this thread! Thanks for your help. Not life or death stuff here, just trying to keep it all clean.
– samsmith
8 hours ago
add a comment |
Identity inserts only apply to identity columns in sql server trying to create non numeric identity columns will produce this error:
Identity column 'id' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, unencrypted, and constrained to be nonnullable.
No uniqueidentifiers allowed.
answered 6 hours ago
jmorenojmoreno
579416
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229673%2fis-set-identity-insert-required-to-insert-arbitrary-guid-into-uniqueidentifie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
IDENTITY_INSERT is only used for columns with the IDENTITY property.
UNIQUEIDENTIFIER is merely a data type.
Your insert statement will work.
answered 8 hours ago
Paul White♦Paul White
52k14278450
Thank you. That is what I also understood. I found it odd that the DBA gave me "SET IDENTITY_INSERT Carrier ON" all over tables that lack the Identity attribute.
– samsmith
8 hours ago
1
@samsmith DBAs can be odd, just like everyone else 😃
– Paul White♦
8 hours ago
I know. It is cool. I know this is not harmful. But if the folks using the SQL from the DBA actually insist on understanding what they are doing (as I do), they will look this stuff up. And when the docs indicate that the DBA is giving superfluous stuff, it opens a can of worms like.... this thread! Thanks for your help. Not life or death stuff here, just trying to keep it all clean.
– samsmith
8 hours ago
add a comment |
IDENTITY_INSERT is only used for columns with the IDENTITY property.
UNIQUEIDENTIFIER is merely a data type.
Your insert statement will work.
answered 8 hours ago
Paul White♦Paul White
52k14278450
Thank you. That is what I also understood. I found it odd that the DBA gave me "SET IDENTITY_INSERT Carrier ON" all over tables that lack the Identity attribute.
– samsmith
8 hours ago
1
@samsmith DBAs can be odd, just like everyone else 😃
– Paul White♦
8 hours ago
I know. It is cool. I know this is not harmful. But if the folks using the SQL from the DBA actually insist on understanding what they are doing (as I do), they will look this stuff up. And when the docs indicate that the DBA is giving superfluous stuff, it opens a can of worms like.... this thread! Thanks for your help. Not life or death stuff here, just trying to keep it all clean.
– samsmith
8 hours ago
add a comment |
IDENTITY_INSERT is only used for columns with the IDENTITY property.
UNIQUEIDENTIFIER is merely a data type.
Your insert statement will work.
answered 8 hours ago
Paul White♦Paul White
52k14278450
IDENTITY_INSERT is only used for columns with the IDENTITY property.
UNIQUEIDENTIFIER is merely a data type.
Your insert statement will work.
answered 8 hours ago
Paul White♦Paul White
52k14278450
answered 8 hours ago
Paul White♦Paul White
52k14278450
answered 8 hours ago
Paul White♦Paul White
52k14278450
answered 8 hours ago
Paul White♦Paul White
52k14278450
52k14278450
Thank you. That is what I also understood. I found it odd that the DBA gave me "SET IDENTITY_INSERT Carrier ON" all over tables that lack the Identity attribute.
– samsmith
8 hours ago
1
@samsmith DBAs can be odd, just like everyone else 😃
– Paul White♦
8 hours ago
I know. It is cool. I know this is not harmful. But if the folks using the SQL from the DBA actually insist on understanding what they are doing (as I do), they will look this stuff up. And when the docs indicate that the DBA is giving superfluous stuff, it opens a can of worms like.... this thread! Thanks for your help. Not life or death stuff here, just trying to keep it all clean.
– samsmith
8 hours ago
add a comment |
Thank you. That is what I also understood. I found it odd that the DBA gave me "SET IDENTITY_INSERT Carrier ON" all over tables that lack the Identity attribute.
– samsmith
8 hours ago
1
@samsmith DBAs can be odd, just like everyone else 😃
– Paul White♦
8 hours ago
I know. It is cool. I know this is not harmful. But if the folks using the SQL from the DBA actually insist on understanding what they are doing (as I do), they will look this stuff up. And when the docs indicate that the DBA is giving superfluous stuff, it opens a can of worms like.... this thread! Thanks for your help. Not life or death stuff here, just trying to keep it all clean.
– samsmith
8 hours ago
Thank you. That is what I also understood. I found it odd that the DBA gave me "SET IDENTITY_INSERT Carrier ON" all over tables that lack the Identity attribute.
– samsmith
8 hours ago
Thank you. That is what I also understood. I found it odd that the DBA gave me "SET IDENTITY_INSERT Carrier ON" all over tables that lack the Identity attribute.
– samsmith
8 hours ago
1
1
@samsmith DBAs can be odd, just like everyone else 😃
– Paul White♦
8 hours ago
@samsmith DBAs can be odd, just like everyone else 😃
– Paul White♦
8 hours ago
I know. It is cool. I know this is not harmful. But if the folks using the SQL from the DBA actually insist on understanding what they are doing (as I do), they will look this stuff up. And when the docs indicate that the DBA is giving superfluous stuff, it opens a can of worms like.... this thread! Thanks for your help. Not life or death stuff here, just trying to keep it all clean.
– samsmith
8 hours ago
I know. It is cool. I know this is not harmful. But if the folks using the SQL from the DBA actually insist on understanding what they are doing (as I do), they will look this stuff up. And when the docs indicate that the DBA is giving superfluous stuff, it opens a can of worms like.... this thread! Thanks for your help. Not life or death stuff here, just trying to keep it all clean.
– samsmith
8 hours ago
add a comment |
Identity inserts only apply to identity columns in sql server trying to create non numeric identity columns will produce this error:
Identity column 'id' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, unencrypted, and constrained to be nonnullable.
No uniqueidentifiers allowed.
answered 6 hours ago
jmorenojmoreno
579416
add a comment |
Identity inserts only apply to identity columns in sql server trying to create non numeric identity columns will produce this error:
Identity column 'id' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, unencrypted, and constrained to be nonnullable.
No uniqueidentifiers allowed.
answered 6 hours ago
jmorenojmoreno
579416
add a comment |
Identity inserts only apply to identity columns in sql server trying to create non numeric identity columns will produce this error:
Identity column 'id' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, unencrypted, and constrained to be nonnullable.
No uniqueidentifiers allowed.
answered 6 hours ago
jmorenojmoreno
579416
Identity inserts only apply to identity columns in sql server trying to create non numeric identity columns will produce this error:
Identity column 'id' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, unencrypted, and constrained to be nonnullable.
No uniqueidentifiers allowed.
answered 6 hours ago
jmorenojmoreno
579416
answered 6 hours ago
jmorenojmoreno
579416
answered 6 hours ago
jmorenojmoreno
579416
answered 6 hours ago
jmorenojmoreno
579416
579416
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229673%2fis-set-identity-insert-required-to-insert-arbitrary-guid-into-uniqueidentifie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
