Viewing 15 posts - 2,251 through 2,265 (of 5,109 total)
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 25, 2018 at 2:22 am
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 24, 2018 at 3:09 pm
Are you expect row 1 to have the same value in both columns, row 2 to have the same value for both columns, row 3 to have...? That's not what...
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 24, 2018 at 2:47 pm
What do you actually mean by this? SQL Server can tell you what user and login is being used in the current session by using CURRENT_USER() and SYSTEM_USER() respectively. Thom~ Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 24, 2018 at 11:27 am
Alternatively, instead of using a Table-type parameter, you could consider passing the value as a delimited string and then using a string splitter.
Either way, Gail is completely right;...
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 24, 2018 at 9:23 am
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 24, 2018 at 3:01 am
The error message is quite clear here: "Transparent Data Encryption is not available in the the edition of this SQL Server instance." Emphasis mine.
As per the Supported Features...
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 24, 2018 at 2:56 am
GilaMonster - Monday, January 22, 2018 6:07 AM
Heh, and this is why I doubted the documentation more than yourself. 🙂
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 22, 2018 at 7:03 am
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 22, 2018 at 1:57 am
But this would just disappear the warning. Let me make it more clear about...
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 21, 2018 at 6:43 am
Yes, you with the following
[Code]SET ANSI_WARNINGS OFF;
--INSERT operation
SET ANSI_WARNINGS ON;[/code]
It's important to remember to switch the warnings back on afterwards.
Personally, however, rather...
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 21, 2018 at 5:44 am
You'll need to use an INSTEAD OF trigger. For example:
USE Sandbox;
GO
CREATE TABLE Table1 (ID int, String varchar(10)); Thom~ Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
CREATE TABLE Table2 (ID int, String varchar(10));
Larnu.uk
January 20, 2018 at 5:07 am
I'm thinking, Phil, this is likely due to our good old friend Mr "Double Hop". If the OP is having issues running it using SSMS, but can do so fine...
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 19, 2018 at 9:03 am
It is there: https://support.microsoft.com/en-mt/hotfix/kbhotfix?kbnum=967909&kbln=en-US
Make sure you click "Show hotfixes for all platforms and languages".
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 19, 2018 at 8:18 am