Viewing 15 posts - 1,816 through 1,830 (of 2,649 total)
possibly another process grabbing the admin session before you can do it.
I would try and use the -m startup option with a program name associated. e.g. -mSQLCMD and then connect...
December 9, 2019 at 4:35 pm
please please do NOT use cursors for this
standard construct for a batch update where you have a KEY (or set of columns) that you can use to filter what has...
December 9, 2019 at 12:10 pm
Sam - did you read my comments?
Adding those indexes are not necessarily what needs to be done (as recommendations from the engine are just that)
and is the field I mentioned...
December 9, 2019 at 11:36 am
I'm curious - do you have 2 processors with 5 cores each with HT active? or 2 * 10 cores = 20 HT?
Regardless of it I would probably change that...
December 9, 2019 at 12:18 am
your "requirements" do not match what you trying to do on the sql so please do clarify it exactly.
To get the records added today - which is what your subquery...
December 8, 2019 at 1:01 pm
you need to learn to explain your requirements better - just stating that for a small sample of data you need this output is not enough.
Even with the latest output...
December 7, 2019 at 6:25 pm
Apologies I should have remove the t1. from the order by when I added the outer select to filter on balance.
Now you have added a further block inside the query....
December 7, 2019 at 1:01 pm
select *
from (
select t1.Account
, isnull(
...
December 7, 2019 at 10:51 am
without having sample data its hard to tell.
but try
$Failed = $csv | Where-Object {$csv.Result -eq 'Failed'}|select -property Batfile
December 7, 2019 at 10:44 am
what was the exact create index statement?
and if this was on the same machine that you have with a maxdop of 1 that is likely normal and in this case...
December 7, 2019 at 10:42 am
Always makes wonder when I see a machine with 12 cores and maxdop = 1.
Has it been proven that for this machine this is the correct setting or was this...
December 7, 2019 at 8:54 am
duplicate entry. Please post any reply on https://www.sqlservercentral.com/forums/topic/developing-ssis-packages-in-vs-2019-and-running-them-on-sql-server-2014-and-2016-2#post-3705508
December 6, 2019 at 6:43 pm
When you create the project on SSDT (VS) you need to select the target SQL Server version - once you select 2014 you can use them on that SQL Version
December 6, 2019 at 6:42 pm
Think that error is on your pc - not the server.
your pc may be struggling or your version of SSMS has issues - better to install the latest one and...
December 3, 2019 at 8:52 pm
if that regulated then installing Visual Studio on the server is also not allowed - again licensing issues.
using OpenXML (2.9 better than 2.5 but harder to install) is one way.
December 3, 2019 at 8:48 pm
Viewing 15 posts - 1,816 through 1,830 (of 2,649 total)