network profile
| bio | website | sqlwebpedia.com |
|---|---|---|
| location | Seattle, WA | |
| age | 40 | |
| visits | member for | 1 year, 5 months |
| seen | Jun 19 '12 at 7:02 | |
| stats | profile views | 8 |
SQL Server Administrator, entrepreneur, family man, Christian. @SQLGuyChuck on twitter.
|
Dec 25 |
awarded | Popular Question |
|
Jun 19 |
answered | replication monitor: why is current average performance poor? |
|
Jun 19 |
answered | replication warning: transactional replication latency alert not working |
|
Jun 19 |
answered | What options exist for copying data between servers on a regular basis? |
|
Jun 19 |
answered | Transactional replication from SQL Server 2000 to 2008 |
|
Apr 7 |
awarded | Student |
|
Dec 8 |
answered | MS SQL Linked Server Security failing using current security context |
|
Dec 8 |
awarded | Teacher |
|
Dec 6 |
comment |
MS SQL Linked Server Security failing using current security context Ah yes, enabled that for testing. I have disabled and still have issue. |
|
Dec 6 |
comment |
MS SQL Linked Server Security failing using current security context I can do a regular select statement, just not a proc call. |
|
Dec 6 |
comment |
MS SQL Linked Server Security failing using current security context @SirSQL on twitter #sqlhelp said: Repl creates it as a remote server which is no longer supported. Found out the hard way. He had to drop repl, create linked server, re-create replication. And another alternative is to create a sql alias and new linked server connection, but I can't as lots of code would have to change. |
|
Dec 6 |
comment |
MS SQL Linked Server Security failing using current security context I changed to proc call as that is ultimately all I am doing. I did test with one of my procs and was able to reproduce. |
|
Dec 6 |
revised |
MS SQL Linked Server Security failing using current security context added create script output of linked server from ssms. |
|
Dec 6 |
comment |
SSAS queries time out when Windows File System Cache drops Could it be IO config issue? What is your disk offset setting? What cluster size on disk are you using? If a SAN, what is HBA queue depth? Are you using latest MPIO drivers? |
|
Dec 6 |
awarded | Editor |
|
Dec 6 |
revised |
MS SQL Linked Server Security failing using current security context changed sql agent job kickoff to just a proc call as easier to understand. |
|
Dec 6 |
comment |
MS SQL Linked Server Security failing using current security context For giggles, I created a new alias for the db03 instance and all worked. It seems the replication created linked server is crippled in some fashion. Need to find a way to get it to work as updating all my code is just not going to work for me. |
|
Dec 6 |
asked | MS SQL Linked Server Security failing using current security context |
|
Dec 6 |
awarded | Autobiographer |
