Probably a bit messy, but what about using a CASE statement? Something along the lines of:

SELECT ID
    , CASE WHEN EXISTS (SELECT 1
 ...

I could be dumb, but I am pretty sure that "server\database" is not a valid way to connect to a SQL instance. It needs to be server\instance. Otherwise how does...

I just want to add some clarity to Scott's reply - it depends. You CAN have your BAT file run synchronously OR asynchronously. It depends on the BAT file. For...

I generally look for all  logs that I am able to access. In this scenario, the SQL logs (not error logs, but the current SQL Server Logs, or possibly a...

My approach when things like this happen is I start my DR (disaster recovery) process. Restore the last known good backup to a test system and then copy the data...

I would start by checking the logs on the publisher and subscriber as those will tell you what is wrong. Likely a permission issue on either the publisher or subscriber,...

It sounds like you have a tool that monitors memory usage on the server. If you want a per-process app that'll do that, perfmon or task manager will monitor your...

Are you meaning per query or overall? and what do you mean by "continuously"? Like you want a realtime constant monitoring of overall memory usage? If so, then the easiest...

Welcome to the dev world then! When I was new to SQL, one of the hardest things I had to wrap my brain around was "row based operations" vs "column...

As a guess, if you select "Insert Row", it should have an option to add it at the top or bottom (if I remember right)... after adding a row, are...

VERY quick look at that, you have a bunch of dynamic SQL which is always a bit risky, so my opinion, I would re-write the whole thing without the dynamic...

VERY quick look at that, you have a bunch of dynamic SQL which is always a bit risky, so my opinion, I would re-write the whole thing without the dynamic...

First step, review the execution plan. Next step, I'd check server resources and server settings. If the query is slower, is the hardware identical? If not, that could be the...

slow inserts are USUALLY caused by either slow network connection between the client machine and the database OR poor indexing strategy on the table OR stored procedure for the insert...

My opinion, I'd redesign the original table to not allow varchar in the column and force ints... but if you are stuck with that, I would look at a string...