The -W switch is not working in SQL Server 2012.

Installed SQL Server 2012. The -W switch doesn't work on SQLCMD. Any ideas why or what to do?

Could you please explain little more?
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Similar Messages

Full Text Search in PDF file Not Working in SQL Server 2012

OS: Windows Server 2012 @ Azure
DB: SQL Server 2012 SP 1 with Cum Update 6
Filter: OfficeFilter installed, PDFFilter64 11 installed (actually I tried 9 too)
I have done the following steps:-
1. Configure SQL Server Instance to enable FILESTREAM for Transaction-SQL Access (IO Access and Allow Remote Client Access to FileStream data) and restart the instance service.
2. Set Stream Access Level to Full Access and
3. Create Database with file stream folder and set the created database Properties.Options: FileStreamDirectorName = fileContainer and FileStream Non-Transaction Access = Full.
4. Create a FileTable with file director
5. Execute the following scripts to ensure all installed components working. PDF is listed as one of the supported filter.
EXEC sp_fulltext_service @action='load_os_resources', @value=1;
EXEC sp_fulltext_service 'verify_signature', 0 -- don't verify signatures
EXEC sp_fulltext_service 'update_languages'; -- update language list
EXEC sp_fulltext_service 'restart_all_fdhosts';
EXEC sp_help_fulltext_system_components 'filter'
reconfigure with override
6. Copy a few PPTX, DOCX, PDF file into the file director.
7. Search the data by following command. I can PPTX and DOCX files can return right result but PDF is not returned although it contains the searching contents.
SELECT *
FROM dbo.Course
WHERE CONTAINS(file_stream, 'Counsellor');
Any expert advise?
Ant in SG

Are you seeing any errors in the SQL Server Error Log, the Windows Application or System logs? How about in the Full-text crawl logging?
Troubleshooting Errors in a Full-Text Population (Crawl)
If your server has a mix of multi-threaded iFilters and single-threaded iFilters, this can cause serious problems with building the full text index. (How do I know this? Well, let's just say that I have suffered as well. And I was shocked!)
The efficiency was greatly increased by this article:
Troubleshooting: Slow Full-Text Indexing Performance Due to Filtering Process
This means changing the threading model for the multi-threaded (e.g. Microsoft Office) filters to be Apartment Threaded. Or perhaps if you are full text indexing PDF files, abandoning the free single-threaded Adobe IFilter and purchasing the FoxIt
(or some other) multi-threaded PDF iFilter would benefit you.
RLF

Transaction Log Truncate not working on Sql Server 2012 High Availability Groups

Hi Everyone
Firstly I have tried to search the forum for similar issues but can't seem to find any that match our situation.
We have a SQL Server 2012 High Availability Group with 2 Nodes
Node 1 = Primary
Node 2 = Secondary
Backup Schedule as follows
Full Database Backup @ 00:00
Transaction Log Backup every 30 minutes from 00:30:00 till 23:59:59.
These backups are run by Maintenance Jobs, but we have also tried doing direct backups in SSMS using Backup Database and Backup Log commands.
Before we configured the High Availability group the transaction log backups worked fine.
After we configured the High Availability group we performed a Full Backup and the T-Log schedule did the T-Log backup. The 1st T-log backup truncated the log (Used space Decreased) as expected.
However subsequent T-Log backups do not truncate the T-Log.
This happens both in our acceptance and Live environments. This also happens when running the backups as a Backup operator and sysadmin, this does not seem to be a permissions issue at all.
We have tried running the Backup on the Primary and Secondary Replica.
What about High Availability groups could stop Transaction Log Backups from not truncating the log?
Thanks
James

Hi Sean
Thank you for your reply, please see the output of the sys.databases query below, and some others which you may find usefull.
Query: select database_id,recovery_model_desc, log_reuse_wait, log_reuse_wait_desc from sys.databases
where database_id = 5
Result: database_id   recovery_model_desc   log_reuse_wait   log_reuse_wait_desc
                 5
FULL   0
NOTHING
I also ran the following
select database_id, truncation_lsn, last_received_lsn, last_commit_lsn, last_hardened_lsn, last_redone_lsn,*
from sys.dm_hadr_database_replica_states
go
database_id
truncation_lsn
last_received_lsn
last_commit_lsn
last_hardened_lsn
last_redone_lsn
database_id
group_id
replica_id
group_database_id
is_local
synchronization_state
synchronization_state_desc
is_commit_participant
synchronization_health
synchronization_health_desc
database_state
database_state_desc
is_suspended
suspend_reason
suspend_reason_desc
recovery_lsn
truncation_lsn
last_sent_lsn
last_sent_time
last_received_lsn
last_received_time
last_hardened_lsn
last_hardened_time
last_redone_lsn
last_redone_time
log_send_queue_size
log_send_rate
redo_queue_size
redo_rate
filestream_send_rate
end_of_log_lsn
last_commit_lsn
last_commit_time
low_water_mark_for_ghosts
5
1231833000417170000000
1231833000418880000000
1231833000418880000000
1231833000418890000000
1231833000418880000000
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
7E8BFC2E-363F-4C48-86F0-C276D3E0C8D9
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
0
2
SYNCHRONIZED
1
2
HEALTHY
NULL
NULL
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
1
41863
1231833000418880000000
41863
1231833000418890000000
41863
1231833000418880000000
41863
0
25541
0
84404
75304
1231833000418880000000
1231833000418880000000
41863
441019861
5
1231833000417170000000
NULL
1231833000418880000000
1231833000418890000000
NULL
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
83B9F00E-D63F-4AC0-98FC-35E48FFA2C6F
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
1
2
SYNCHRONIZED
1
2
HEALTHY
0
ONLINE
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
NULL
NULL
NULL
NULL
1231833000418890000000
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
1231833000418880000000
1231833000418880000000
41863
441019861
And
dbcc loginfo
go
RecoveryUnitId
FileId
FileSize
StartOffset
FSeqNo
Status
Parity
CreateLSN
0
2
458752
8192
1231828
0
128
0
0
2
458752
466944
1231829
0
128
0
0
2
458752
925696
1231830
0
128
0
0
2
712704
1384448
1231831
0
128
0
0
2
19398656
2097152
1231832
0
128
1229654000000040000000
0
2
10199171072
21495808
1231833
2
128
1229656000000010000000
0
2
10199171072
10220666880
0
0
64
1229656000000010000000
0
2
10199171072
20419837952
1231827
0
64
1229656000000010000000
0
2
10199171072
30619009024
0
0
128
1229656000000010000000
0
2
10199171072
40818180096
0
0
128
1229656000000010000000
0
2
10199171072
51017351168
0
0
128
1229656000000010000000
0
2
10199171072
61216522240
0
0
128
1229656000000010000000
0
2
10199171072
71415693312
0
0
128
1229656000000010000000
0
2
10199171072
81614864384
0
0
128
1229656000000010000000
0
2
536870912
91814035456
0
0
64
1229989001661260000000
0
2
536870912
92350906368
0
0
64
1229989001661260000000
0
2
536870912
92887777280
0
0
64
1229989001661260000000
0
2
536870912
93424648192
0
0
64
1229989001661260000000
0
2
536870912
93961519104
0
0
64
1229989001661260000000
0
2
536870912
94498390016
0
0
64
1229989001661260000000
0
2
536870912
95035260928
0
0
64
1229989001661260000000
0
2
536870912
95572131840
0
0
64
1229989001661260000000
0
2
536870912
96109002752
0
0
64
1229989001661260000000
0
2
536870912
96645873664
0
0
64
1229989001661260000000
0
2
536870912
97182744576
0
0
64
1229989001661260000000
0
2
536870912
97719615488
0
0
64
1229989001661260000000
0
2
536870912
98256486400
0
0
64
1229989001661260000000
0
2
536870912
98793357312
0
0
64
1229989001661260000000
0
2
536870912
99330228224
0
0
64
1229989001661260000000
0
2
536870912
99867099136
0
0
64
1229989001661260000000
0
2
536870912
100403970048
0
0
64
1229995000058520000000
0
2
536870912
100940840960
0
0
64
1229995000058520000000
0
2
536870912
101477711872
0
0
64
1229995000058520000000
0
2
536870912
102014582784
0
0
64
1229995000058520000000
0
2
536870912
102551453696
0
0
64
1229995000058520000000
0
2
536870912
103088324608
0
0
64
1229995000058520000000
0
2
536870912
103625195520
0
0
64
1229995000058520000000
0
2
536870912
104162066432
0
0
64
1229995000058520000000
0
2
536870912
104698937344
0
0
64
1229995000058520000000
0
2
536870912
105235808256
0
0
64
1229995000058520000000
0
2
536870912
105772679168
0
0
64
1229995000058520000000
0
2
536870912
106309550080
0
0
64
1229995000058520000000
0
2
536870912
106846420992
0
0
64
1229995000058520000000
0
2
536870912
107383291904
0
0
64
1229995000058520000000
0
2
536870912
107920162816
0
0
64
1229995000058520000000
0
2
536870912
108457033728
0
0
64
1229995000058520000000
0
2
536870912
108993904640
0
0
64
1230004000028400000000
0
2
536870912
109530775552
0
0
64
1230004000028400000000
0
2
536870912
110067646464
0
0
64
1230004000028400000000
0
2
536870912
110604517376
0
0
64
1230004000028400000000
0
2
536870912
111141388288
0
0
64
1230004000028400000000
0
2
536870912
111678259200
0
0
64
1230004000028400000000
0
2
536870912
112215130112
0
0
64
1230004000028400000000
0
2
536870912
112752001024
0
0
64
1230004000028400000000
0
2
536870912
113288871936
0
0
64
1230004000028400000000
0
2
536870912
113825742848
0
0
64
1230004000028400000000
0
2
536870912
114362613760
0
0
64
1230004000028400000000
0
2
536870912
114899484672
0
0
64
1230004000028400000000
0
2
536870912
115436355584
0
0
64
1230004000028400000000
0
2
536870912
115973226496
0
0
64
1230004000028400000000
0
2
536870912
116510097408
0
0
64
1230004000028400000000
0
2
536870912
117046968320
0
0
64
1230004000028400000000
0
2
536870912
117583839232
0
0
64
1230012000103140000000
0
2
536870912
118120710144
0
0
64
1230012000103140000000
0
2
536870912
118657581056
0
0
64
1230012000103140000000
0
2
536870912
119194451968
0
0
64
1230012000103140000000
0
2
536870912
119731322880
0
0
64
1230012000103140000000
0
2
536870912
120268193792
0
0
64
1230012000103140000000
0
2
536870912
120805064704
0
0
64
1230012000103140000000
0
2
536870912
121341935616
0
0
64
1230012000103140000000
0
2
536870912
121878806528
0
0
64
1230012000103140000000
0
2
536870912
122415677440
0
0
64
1230012000103140000000
0
2
536870912
122952548352
0
0
64
1230012000103140000000
0
2
536870912
123489419264
0
0
64
1230012000103140000000
0
2
536870912
124026290176
0
0
64
1230012000103140000000
0
2
536870912
124563161088
0
0
64
1230012000103140000000
0
2
536870912
125100032000
0
0
64
1230012000103140000000
0
2
536870912
125636902912
0
0
64
1230012000103140000000
0
2
536870912
126173773824
0
0
128
1230338000973820000000
0
2
536870912
126710644736
0
0
128
1230338000973820000000
0
2
536870912
127247515648
0
0
128
1230338000973820000000
0
2
536870912
127784386560
0
0
128
1230338000973820000000
0
2
536870912
128321257472
0
0
128
1230338000973820000000
0
2
536870912
128858128384
0
0
128
1230338000973820000000
0
2
536870912
129394999296
0
0
128
1230338000973820000000
0
2
536870912
129931870208
0
0
128
1230338000973820000000
0
2
536870912
130468741120
0
0
128
1230338000973820000000
0
2
536870912
131005612032
0
0
128
1230338000973820000000
0
2
536870912
131542482944
0
0
128
1230338000973820000000
0
2
536870912
132079353856
0
0
128
1230338000973820000000
0
2
536870912
132616224768
0
0
128
1230338000973820000000
0
2
536870912
133153095680
0
0
128
1230338000973820000000
0
2
536870912
133689966592
0
0
128
1230338000973820000000
0
2
536870912
134226837504
0
0
128
1230338000973820000000
0
2
536870912
134763708416
0
0
128
1230338001901440000000
0
2
536870912
135300579328
0
0
128
1230338001901440000000
0
2
536870912
135837450240
0
0
128
1230338001901440000000
0
2
536870912
136374321152
0
0
128
1230338001901440000000
0
2
536870912
136911192064
0
0
128
1230338001901440000000
0
2
536870912
137448062976
0
0
128
1230338001901440000000
0
2
536870912
137984933888
0
0
128
1230338001901440000000
0
2
536870912
138521804800
0
0
128
1230338001901440000000
0
2
536870912
139058675712
0
0
128
1230338001901440000000
0
2
536870912
139595546624
0
0
128
1230338001901440000000
0
2
536870912
140132417536
0
0
128
1230338001901440000000
0
2
536870912
140669288448
0
0
128
1230338001901440000000
0
2
536870912
141206159360
0
0
128
1230338001901440000000
0
2
536870912
141743030272
0
0
128
1230338001901440000000
0
2
536870912
142279901184
0
0
128
1230338001901440000000
0
2
536870912
142816772096
0
0
128
1230338001901440000000
0
2
536870912
143353643008
0
0
128
1230346000103040000000
0
2
536870912
143890513920
0
0
128
1230346000103040000000
0
2
536870912
144427384832
0
0
128
1230346000103040000000
0
2
536870912
144964255744
0
0
128
1230346000103040000000
0
2
536870912
145501126656
0
0
128
1230346000103040000000
0
2
536870912
146037997568
0
0
128
1230346000103040000000
0
2
536870912
146574868480
0
0
128
1230346000103040000000
0
2
536870912
147111739392
0
0
128
1230346000103040000000
0
2
536870912
147648610304
0
0
128
1230346000103040000000
0
2
536870912
148185481216
0
0
128
1230346000103040000000
0
2
536870912
148722352128
0
0
128
1230346000103040000000
0
2
536870912
149259223040
0
0
128
1230346000103040000000
0
2
536870912
149796093952
0
0
128
1230346000103040000000
0
2
536870912
150332964864
0
0
128
1230346000103040000000
0
2
536870912
150869835776
0
0
128
1230346000103040000000
0
2
536870912
151406706688
0
0
128
1230346000103040000000
0
2
536870912
151943577600
0
0
128
1230355000086930000000
0
2
536870912
152480448512
0
0
128
1230355000086930000000
0
2
536870912
153017319424
0
0
128
1230355000086930000000
0
2
536870912
153554190336
0
0
128
1230355000086930000000
0
2
536870912
154091061248
0
0
128
1230355000086930000000
0
2
536870912
154627932160
0
0
128
1230355000086930000000
0
2
536870912
155164803072
0
0
128
1230355000086930000000
0
2
536870912
155701673984
0
0
128
1230355000086930000000
0
2
536870912
156238544896
0
0
128
1230355000086930000000
0
2
536870912
156775415808
0
0
128
1230355000086930000000
0
2
536870912
157312286720
0
0
128
1230355000086930000000
0
2
536870912
157849157632
0
0
128
1230355000086930000000
0
2
536870912
158386028544
0
0
128
1230355000086930000000
0
2
536870912
158922899456
0
0
128
1230355000086930000000
0
2
536870912
159459770368
0
0
128
1230355000086930000000
0
2
536870912
159996641280
0
0
128
1230355000086930000000
0
2
536870912
160533512192
0
0
128
1230364000070870000000
0
2
536870912
161070383104
0
0
128
1230364000070870000000
0
2
536870912
161607254016
0
0
128
1230364000070870000000
0
2
536870912
162144124928
0
0
128
1230364000070870000000
0
2
536870912
162680995840
0
0
128
1230364000070870000000
0
2
536870912
163217866752
0
0
128
1230364000070870000000
0
2
536870912
163754737664
0
0
128
1230364000070870000000
0
2
536870912
164291608576
0
0
128
1230364000070870000000
0
2
536870912
164828479488
0
0
128
1230364000070870000000
0
2
536870912
165365350400
0
0
128
1230364000070870000000
0
2
536870912
165902221312
0
0
128
1230364000070870000000
0
2
536870912
166439092224
0
0
128
1230364000070870000000
0
2
536870912
166975963136
0
0
128
1230364000070870000000
0
2
536870912
167512834048
0
0
128
1230364000070870000000
0
2
536870912
168049704960
0
0
128
1230364000070870000000
0
2
536870912
168586575872
0
0
128
1230364000070870000000
0
2
536870912
169123446784
0
0
128
1230373000054750000000
0
2
536870912
169660317696
0
0
128
1230373000054750000000
0
2
536870912
170197188608
0
0
128
1230373000054750000000
0
2
536870912
170734059520
0
0
128
1230373000054750000000
0
2
536870912
171270930432
0
0
128
1230373000054750000000
0
2
536870912
171807801344
0
0
128
1230373000054750000000
0
2
536870912
172344672256
0
0
128
1230373000054750000000
0
2
536870912
172881543168
0
0
128
1230373000054750000000
0
2
536870912
173418414080
0
0
128
1230373000054750000000
0
2
536870912
173955284992
0
0
128
1230373000054750000000
0
2
536870912
174492155904
0
0
128
1230373000054750000000
0
2
536870912
175029026816
0
0
128
1230373000054750000000
0
2
536870912
175565897728
0
0
128
1230373000054750000000
0
2
536870912
176102768640
0
0
128
1230373000054750000000
0
2
536870912
176639639552
0
0
128
1230373000054750000000
0
2
536870912
177176510464
0
0
128
1230373000054750000000
0
2
536870912
177713381376
0
0
128
1230382000038660000000
0
2
536870912
178250252288
0
0
128
1230382000038660000000
0
2
536870912
178787123200
0
0
128
1230382000038660000000
0
2
536870912
179323994112
0
0
128
1230382000038660000000
0
2
536870912
179860865024
0
0
128
1230382000038660000000
0
2
536870912
180397735936
0
0
128
1230382000038660000000
0
2
536870912
180934606848
0
0
128
1230382000038660000000
0
2
536870912
181471477760
0
0
128
1230382000038660000000
0
2
536870912
182008348672
0
0
128
1230382000038660000000
0
2
536870912
182545219584
0
0
128
1230382000038660000000
0
2
536870912
183082090496
0
0
128
1230382000038660000000
0
2
536870912
183618961408
0
0
128
1230382000038660000000
0
2
536870912
184155832320
0
0
128
1230382000038660000000
0
2
536870912
184692703232
0
0
128
1230382000038660000000
0
2
536870912
185229574144
0
0
128
1230382000038660000000
0
2
536870912
185766445056
0
0
128
1230382000038660000000
The create LSN column seems to have been truncated so here is is again, sorry for the bulky reply.
CreateLSN
0
0
0
0
1229654000000041600001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
Thanks
James

SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

I am working in a Product based company.
We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
I have used "Script Component" in my package.
We will take only DTSX package file to the customer places and run using SQL Agent Job daily.
Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
Who are all(Customer Environments) using SQL 2012, I am facing the below issue
The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Still the same package is running fine for some of the customers having SQL 2012.
I am getting the above error only for few customers.
Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

Hi Katherine,
I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
Here is my Simple .net code
/* Microsoft SQL Server Integration Services Script Component
* Write scripts using Microsoft Visual C# 2008.
* ScriptMain is the entry point class of the script.*/
using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
public override void PreExecute()
base.PreExecute();
Add your code here for preprocessing or remove if not needed
public override void PostExecute()
base.PostExecute();
Add your code here for postprocessing or remove if not needed
You can set read/write variables here, for example:
Variables.MyIntVar = 100
int counter = 0;
public override void Input0_ProcessInputRow(Input0Buffer Row)
if (counter == 0)
counter = Convert.ToInt32(Row.JurisCount);
Row.JurisKey = counter;
counter = counter + 1;
PAVAN MSBI

EXEC SP_EXECUTESQL not working in sql server 2014

EXEC SP_EXECUTESQL not working in sql server 2014

EXEC SP_EXECUTESQL not working in sql server 2014
Hi Amar,
What's the error when executing this stored procedure?
I have tested it on my local environment, we can run this SP without any problems.
Please provide us more information, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Database Mail not working with SQL Server Agent

I'm running SQL Server 2005 Standard edition 64 bit with SP2 on a 64 bit machine.
Database mail does not work with SQL Server Agent. When I configure SQL Server Agent to use database mail the test email button is greyed out and inactive therefore I cannot send emails using operators or for jub success failure etc.
I've read that there was supposed to be a fix for this with SP1 but I have SP2 and still receive the same problem. Please can somebody help as I do not wish to use SQL Mail as a work around due to this becomming redundant in future versions of SQL Server.
Kind Regards

The problems solved
steps:
1)we create a mail profile at at Managment->Database Mail ,of SQL Managment
2)we set this account as "default" at Managment->Database Mail -> Configure Database Mail -> Manage profile security
3)At tab "Alert System" of SQL Server Agent properties , we check the "Enable mail profile" , Mail System=Database Mail, Mail profile = "the profile we already create"
4)we create a new operator at "Operators" of sql agent, where at "notification options" -> "Email name" we put the mail where we want to sent the agent the mails at failured job
5)We go at a specific job, at tab "Notifications" ,we check the "email" check box and then we choose the operator we just create, at the text box next to check box.
I hope not to forget something
Thank You all for the help

What are all the features not supported in SQL Server 2012 trial version?

What are all the features not supported in SQL Server 2012 trial version?

The evaluation edition supports all features and expires after 180 days.
https://msdn.microsoft.com/en-us/library/cc645993.aspx?f=255&MSPPError=-2147217396

The lock switch is not working anymore

The lock switch on my nano doesn't work anymore, it's really annoying since I can't walk around with it in my pocket without the sound getting turned up or the song switched every time i move. Also, since the lock isn't working I can't turn it off properly. Is it a mechanical problem?
Thanks

Are you able to go to an Apple Store? I had an older generation model nano, which the lock switch wasn't working and since it was still under applecare warranty, they replaced the old nano for me. But that is in the USA, so I am not sure how it works in the UK.

Unable to unlock rotation, as the rotations switch is not working

I am unable to unlock the rotation of my ipad 2, the rotation switch on the side above the volume button is not working. However I also cannot allocate the Home button.
Can anyone assist me.
Thank u

Try the stamdard fixes to rule out a software problem:
- Reset. Nothing will be lost
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Restore from backup
- Restore to factory defaults/new iPod.

Distributed transaction using linked server not working in SQL Server 2008 64 bit

Hi. I have had an issue trying to get distributed transactions to work in SQL Server 2008 using a linked server. The error message I get is
OLE DB provider "SQLNCLI10" for linked server "pod1" returned message "No transaction is active.".
Msg 7391, Level 16, State 2, Line 3
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "pod1" was unable to begin a distributed transaction.
My Environment:
Windows Server 2008 Enterprise 64 bit, SQL Server 2008 Enterprise 64 bit
Problem occurs with multiple different builds of SQL Server 2008 - I have been able to reproduce the problem with 10.0.1600.0, 10.0.1779.0 (CU 2), as well as 10.0.2531 (SP1)
I am aware that other people have had this issue and have reviewed all existing posts. I have verified that the MSDTC is configured correctly on both machines. I have also used DTCTester to verify that DTC is working correctly on all machines in question.
None of the mentioned resolutions has solved this problem for me.
I am not seeing this problem occur on my 32 bit test machines - it is only occurring if at least one of the two machines is 64 bit.

Hi All,
I realise that this topic may be a little bit out-of-date but if someone gets here from some search engine trying to find a solution for DTC problems, this MAY be useful.
So... I recently had the same issue, tried all the approaches described in KB and other articles, but it didn't help. Because my task to solve this was not of the highest priority I forgot about it for some time.
Today I was troubleshooting some other issue and, by accident discovered source of that first problem:
In the EventViewer I found Error entry logged by MSDTC saying:
"The local MS DTC detected that the MS DTC on vm-server1 (other machine name that also runs DTC - my comment) has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate
with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install'
from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information."
So I followed suggestion and run:
msdtc -uninstall
msdtc -install
This solved my problems with DTC. Hope it will help someone.
Piotr

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

XP_DELETE_FILE NOT WORKING IN SQL SERVER 2005 SP2

Hi All,
I have one job in sql 2005 sp2 that deletes backup older than one week.It is not working.I have checked service account permissions on backup folder and all required permissions and authentications are in place.Please let me know how to troubleshoot the
same.
Regards
Rahul

Check the following:
http://stackoverflow.com/questions/212603/sql-server-xp-delete-file-not-deleting-files
QUOTE: "Note that xp_delete_file is broken in SP2 and won't work on report files;"
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Could not connect to SQL Server 2012 Remotely

Hello,
I have a situation as follows:
The Server
SQL Server 2012 Standard Edition installed on Windows Server 2012 Standard Edition
Active Directory is installed on the same server as well
Remote Access Role added and configured to connect VPN
DNS Role added
Windows Firewall is disabled
The Server is connected to the internet
SQL Server Service & SQL Browser both are running under domain accounts
SQL Server allows remote connections
The Router
The router that connects the server to the Internet is configured to:
Enable VPN Tunnels Protocols (PPTP, L2TP and IPSec)
Forwarding > Virtual Servers (all requests on TCP and UDP on all ports to the server local IP)
The Client
PC running Windows 7 SP1 with SQL Server 2012 Express
Joined AD on the server
Connected to the internet
VPN Connected to the Server
Can Remote Desktop the Server
Can ping the server host name
Can nslookup the server host name
The Problem
If Both the Server and the Client are connected in the same Local Area Network, Client can connect to the SQL Serve
Once the Client is placed in different location connected to the Interent, VPN connected as described above, I could not connect to the Server using:
Windows Authentication Domain Users or
SQL Server users
and the error message is:
Cannot connect to SERVER\SQLINSTANCE.
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Any thoughts
Thanks in advance

Hello Hilary,
I have been working on a small replication test.
On the Publisher, things went smooth and the Snapshot Agent was able to work and produce a snapshot written in a shared folder located on the Publisher
On the Subscriber, as I am testing from SQL Server Express, I had run the following command:
replmerg.exe -Publisher [SERVER\SQLInstance] -PublisherDB [dbRepl] -PublisherSecurityMode 0 -PublisherLogin rplMergeAgent -PublisherPassword p@ssw0rd -Publication [TEST Publication] -Distributor [SERVER\SQLInstance] -DistributorSecurityMode 0 -DistributorLogin
rplMergeAgent -DistributorPassword p@ssw0rd -Subscriber [SUBSCRIBER\SQLInstance] -SubscriberSecurityMode 0 -SubscriberLogin rplMergeAgent -SubscriberPassword p@ssw0rd -SubscriberDB [dbRepl] -SubscriptionType 1 -OutputVerboseLevel 2 -Output C:\TEMP\mergeagent.log
Where
SERVER
Publisher and Distributor
dbRepl
Database to replicate
Merge Agent
rplMergeAgent
Subscriber
SUBSCRIBER
dbRepl
Subscriber Database
Merge Agent
rplMergeAgent
Password
p@ssw0rd
rplMergeAgent
SQL Login defined in both Publisher and Subscriber with same password
Granted the following at Publisher:
Login to Publication Database (dbRepl)
Login to Distribution Database (distribution)
Member of PAL
Granted the following at Subscriber:
db_owner fixed database role in Subscription database (dbRepl)
I couldn't grant rplMergeAgent Read Permission on SnapshotFolder as it is only a SQL Login.
When I ran the above command line, I received the following error:
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
I am pasting below the whole log file written by the above command:
2014-04-11 15:38:07.205 Microsoft SQL Server Merge Agent 11.0.2218.0
2014-04-11 15:38:07.342 Copyright (c) 2008 Microsoft Corporation
2014-04-11 15:38:07.389
2014-04-11 15:38:07.406 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-04-11 15:38:07.433 User-specified agent parameter values:
-Publisher SERVER\SQLInstance
-PublisherDB dbRepl
-PublisherSecurityMode 0
-PublisherLogin rplMergeAgent
-PublisherPassword **********
-Publication TEST Publication
-Distributor SERVER\SQLInstance
-DistributorSecurityMode 0
-DistributorLogin rplMergeAgent
-DistributorPassword **********
-Subscriber SUBSCRIBER\SQLInstance
-SubscriberSecurityMode 0
-SubscriberLogin rplMergeAgent
-SubscriberPassword **********
-SubscriberDB dbRepl
-SubscriptionType 1
-OutputVerboseLevel 2
-Output C:\TEMP\mergeagent.log
2014-04-11 15:38:07.497 Percent Complete: 0
2014-04-11 15:38:07.517 Connecting to Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:38:07.518 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:07.608 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:07.613 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:07.617 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select
collationproperty(@collation, N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) &
0x1 = 0x1 then 0 else 1 end as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:07.637 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {?=call sp_helpsubscription_properties (N'SERVER\SQLInstance', N'dbRepl', N'TEST Publication')}
2014-04-11 15:38:07.681 Distributor security mode: 0, login name: rplMergeAgent, password: ********.
2014-04-11 15:38:07.682 Percent Complete: 0
2014-04-11 15:38:07.683 Connecting to Distributor 'SERVER\SQLInstance'
2014-04-11 15:38:07.684 Connecting to OLE DB Distributor at datasource: 'SERVER\SQLInstance', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:25.062 OLE DB Distributor: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name:
user name: guest
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:28.887 OLE DB Distributor 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:29.842 OLE DB Distributor 'SERVER\SQLInstance': {call sp_helpdistpublisher (N'SERVER\SQLInstance') }
2014-04-11 15:38:32.198 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:38:33.199 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_merge_agentid (0,N'dbRepl',N'TEST Publication',null,N'dbRepl',100,N'SUBSCRIBER\SQLInstance')}
2014-04-11 15:38:34.451 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:34.560 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_profile (23, 4, N'')}
2014-04-11 15:38:36.189 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:36.499 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_get_redirected_publisher(N'SERVER\SQLInstance',N'dbRepl',0)}
2014-04-11 15:38:37.396 Percent Complete: 0
2014-04-11 15:38:37.396 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.399 Initializing
2014-04-11 15:38:37.401 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.403 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:38.427 Percent Complete: 0
2014-04-11 15:38:38.428 Validating publisher
2014-04-11 15:38:38.429 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:39.455 Percent Complete: 0
2014-04-11 15:38:39.456 Connecting to Publisher 'SERVER\SQLInstance'
2014-04-11 15:38:39.457 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:46.548 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:50.282 OLE DB Publisher 'SERVER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:57.393 OLE DB Publisher 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:59.236 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:39:07.271 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:39:45.229 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.234 Percent Complete: 0
2014-04-11 15:39:45.235 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.236 Retrieving publication information
2014-04-11 15:39:45.238 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:46.287 Percent Complete: 0
2014-04-11 15:39:46.288 Retrieving subscription information.
2014-04-11 15:39:46.290 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.472 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.478 Percent Complete: 0
2014-04-11 15:40:00.479 Applying the snapshot to the Subscriber
2014-04-11 15:40:00.480 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:02.535 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:40:03.559 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_mergesubentry_indistdb (0,N'SERVER\SQLInstance',N'dbRepl',N'TEST Publication',N'SUBSCRIBER\SQLInstance',N'dbRepl',1,1,0,N'',?,90)}
2014-04-11 15:40:04.600 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:40:04.609 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:04.611 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:07.454 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSacquiresnapshotdeliverysessionlock
2014-04-11 15:40:07.526 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MStrypurgingoldsnapshotdeliveryprogress
2014-04-11 15:40:07.530 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSissnapshotitemapplied @snapshot_session_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\', @snapshot_progress_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST
PUBLICATION\20140411082109\Person_2.sch'
2014-04-11 15:40:24.659 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSreleasesnapshotdeliverysessionlock
2014-04-11 15:40:24.663 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.665 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:24.690 Percent Complete: 18
2014-04-11 15:40:24.692 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.693 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:27.541 Percent Complete: 0
2014-04-11 15:40:27.542 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:28.563 Percent Complete: 0
2014-04-11 15:40:28.565 Category:AGENT
Source: SUBSCRIBER\SQLInstance
Number: 0
Message: The process could not read file '\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\Person_2.sch' due to OS error 1326.
2014-04-11 15:40:28.566 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.568 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.569 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.570 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.571 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.573 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.575 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.577 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.578 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
2014-04-11 15:40:28.579 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
I can say it is about how can the rplMergeAgent read the Shared folder.
What do you think?

Data types not compatible with Sql Server 2012

HI All,
I need to know what are data types which were present in sql server 2005 but are not in sql server 2012.
Regards
Rahul

Hi vaibhav
Thanks for help. Actually my requirement is that I have one database on sql server 2005 version. I am planning to migrate it to sql server 2012 version. I want to publish a list of all objects across all databases which cannot be replicated to sql server
2012.How can I do this. Are there any data types which were in sql 2005 version but are depreciated in sql server 2012
Regards
Rahul
yes there are
but why not look at here for breaking changes
http://msdn.microsoft.com/en-us/library/ms143179(v=sql.110).aspx
The deprecated features would still work though new development using them is discouraged
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

MFA not working on Windows Server 2012 R2

Been using MFA since PF days. Deployed it successfully many times but for some reason it's not working with Windows Auth, Terminal Services on a Win 2012 R2 DataCenter box? The machine was successfully added to my domain PhoneFactor group, I
can see and add the machine on the master MFA. Services are running but when I remote in I go right through without MFA stopping me? Any ideas?
TIA

6.3.0 has just been released and 2012 R2 is *still* not supported. What the hell?!?
"Version 6.3.0 of the Azure Multi-Factor Authentication Server adds the
following additional functionality:
* Added one-way SMS functionality for AD FS, RADIUS and User Portal
* Added .csv file import for OATH tokens
* Added support to parse phone numbers in E.164 format during import
From the directory
* Fixed problem preventing slave servers from performing MFA if the
master server was unavailable. This problem was found to exist in
all 6.2.x builds. All customers running 6.2.x should upgrade to 6.3.
* Fixed directory sync issue for recursive security groups
* Added additional logging to AD FS adapter
* Other minor bug fixes and security improvements
Known Issues:
* Windows Authentication for Terminal Services is still not supported for
Windows Server 2012 R2"
So they added a whole stack of other functionality, but still didn't get around to taking a look at this bug. I'm stunned. Is there any sort of timeline on fixing this, or is 2012 R2 just going to remain unsupported forever?

The -W switch is not working in SQL Server 2012.

Similar Messages

Maybe you are looking for