you need to have an explicit ORDER BY in your query. otherwise, it's coincidence or a crapshoot.

SQL server does not have a concept of order in a table.

SQL will...

i would guess your user is a sysadmin, by mistake or due to mutliple roles.

easy to check:

select IS_SRVROLEMEMBER('sysadmin','mydomain\lowell')

GilaMonster (6/8/2016)

---

Don't try to modify a system object (sys.server_triggers), just query the tables directly (and you don't need that conversion function, so omit the lines that use it). sysschobjs is...

import wizard is probably dropping and recreating the tables;

the existing table says NOT NULL,

but whatever the wizard creates allows nulls.

pretty easy to check, compare the table definitions.

saved to file? i am pretty sure you need a system...

TexasJohn (6/8/2016)

---

Nope. C,D & E only. So there are two things going on here. The catalog is wrong and the DSN file Schedule64 was saved to the...

mapped drives like the z: drive are per user.

if you run xp_fixeddrives, do you have a Z:\ drive?

Welsh Corgi (6/8/2016)

---

I am getting a Primary Key Violation when Loading a Table.

I queried the source table and there is only one record with value of the primary key.

This does...

There's no difference ETL wise.

having SPARSE columns lets SQL optimize for mostly null values, and that's under the hood, albeit potentially a bit slower.

I think of sparse columns the same...

I found this interesting, so i duplicated your issue.

I created a couple of server triggers, backed up master and restored it as a new name [masterbackup]

even though i've connecting via...

also, check your schema changes history. if not too much time has occurred, the definition might still be in the default trace.

Sure, its part of a scripti share here that checks for all invalid objects. It triesto recompile procs, functions and views.

sp_InvalidObects.txt

yes, but it's TWO tables that are affected. you want to truncate both parameters and events. i think it might require a DELETE, as i think there is a foreign...

tiny tables.

small tables will not benefit from reindexing. only your large tables.

offhand, i think it's 1000 rows or less don't get any fragmentation benefit/results from reindexing, but we could look...

i've done something similar.

i use sys.views and not information schemas; there's a LOT of information missing in those compatiblity views, so i avoid them like the plague.

select

'exec...