Viewing 15 posts - 136 through 150 (of 7,191 total)
Why do 53 and 924 go in the first row of your results and 54 and 920 in the second? Is it because that's the order they were inserted into...
March 2, 2020 at 4:25 pm
The only thing I can think of is maybe you've reached a size limit on your security event log?
John
March 2, 2020 at 9:00 am
Not much you can do, I'm afraid. You either wait for the transaction to finish (in which case you may need to add more log space) or abort it (in...
February 21, 2020 at 3:34 pm
INSERT INTO inserts into an existing table. SELECT INTO creates a new table and inserts into that - all in one operation.
John
February 21, 2020 at 3:18 pm
I don't know, but you could find out by doing a SELECT INTO and inspecting the definition of the ensuing table.
John
February 21, 2020 at 3:03 pm
OK, so you've got numbers with decimal components, but you want to convert them to int? What is the rule - disregard everything after the decimal point, round to the...
February 21, 2020 at 2:08 pm
Yes, provided all the values in the column can be converted to int. If you have values such as 'Cuttlefish' and 'Madonna' then it's not going to work. The best...
February 21, 2020 at 1:38 pm
You didn't answer the question about whether the SQL Server Agent account is explicitly created as a login
-- This may not work if the SQL Server Agent...
February 21, 2020 at 10:25 am
Permissions is the obvious thing. Assuming your job doesn't use a proxy, it'll run in the context of the SQL Server Agent service account. If you use an EXECUTE AS...
February 21, 2020 at 9:37 am
What is the location of the security log? Does the SQL Server service account have access to it?
John
February 21, 2020 at 9:14 am
February 20, 2020 at 3:58 pm
Yes, the additional storage is the main drawback, although that stops disk from being the only single point of failure. You also need to be careful to match up the...
February 20, 2020 at 2:09 pm
Ah, right - yes. I wondered whether we might be talking at cross-purposes. Makes sense now.
John
February 20, 2020 at 2:00 pm
Grant, I don't think that's true:
-- Execute on SQL Server 2019 server
RESTORE DATABASE Test
FROM DISK = '\\Path\to\backup\of\SQL2016\Database.bak'
WITH NORECOVERY,
MOVE 'DataFile' TO 'X:\MSSQL\SQLData\Test_Data.MDF',
MOVE 'LogFile' TO 'X:\MSSQL\SQLLog\Test_log.ldf';
RESTORE DATABASE Test WITH...
February 20, 2020 at 12:58 pm
The compatibility level of the restored database will be 130 (SQL Server 2016). You can indeed change it to 140 or 150 if you wish.
John
February 20, 2020 at 11:09 am
Viewing 15 posts - 136 through 150 (of 7,191 total)