|
Ntext
|
Nvarchar(max)
|
Default Behavior
|
Data is stored as a LOB
|
Stores data in-row
|
Data is stored
|
Out of the data page as
LOB
|
Stored data In-Row ( if less than 4000)
Stored as LOB ( when more than 4000)
|
Read-aHead Reads
|
All the rows are read-ahead every time. Does not seems to depend on the cache
|
Didn’t read-ahead during the testing
|
Elapse time to insert 200 records
Ex insert into testTable1 select REPLICATE('ABBD455',2000)
go 200
|
High
|
Low
|
One of the clients needed its users to remotely execute a SQL job and as usual I picked this up hoping for a quick brownie point. Sure enough there was a catch and there was something to learn. Executing the job through SQLCMD was a no-brainer but getting it to execute on the remote machine was bit of challenge. On the coding Front 1 1.) The bat file included the following code SQLCMD -S "[ServerName] " -E -Q "EXEC MSDB.dbo.sp_start_job @Job_Name = ' '[JobName]" 2 2.) The Individual users were given minimum permissions to execute the SQL job Ex. use msdb EXECUTE sp_addrolemember @rolename = 'SQLAgentOperatorRole', @membername = ' Domain\UserLogin ' At the client machine This took a fair bit of time till our sysadmin got me an empty VM machine....
Comments
Post a Comment