Snapshots are intrinsic to all three types of replication. I'd recommend you read everything you can find in BOL about replication and maybe read the replication chapter in a book...

Its a registry key, HKLM\Software\Microsoft SQL Server\instance\MSSQLServer, key is BackupDirectory. Should be able to get it from there.

Andy

http://www.sqlservercentral.com/columnists/awarren/

If you use merge there is the possibility that a row could get modified on both publisher and subscriber, creating a conflict - which update wins? MS has built in...

I dont think automatically, have to issue the sync command somehow. There is a Win component that will do it, or you could via SQL. Honestly havent tried that, but...

Two main ways. One is merge replication, really made for those type of situations, or transaction with immediate update/queued update subscribers. I believe it is possible to do true bi...

Possibly #1 will work, but definitely would want to test it before committing. #2 is going to get expensive, but is not a bad strategy. #3 you can split the...

I think opening/closing the connection as you and relying on connection pooling is the way to go. Definitely dont want to hold a connection for every user. If you have...

I'll look. Dont know how much I'll help, but I'll look!

Andy

http://www.sqlservercentral.com/columnists/awarren/

You can actually script out the trigger directly by using the Object Browser to locate it, right click, script as create, alter, etc

Andy

http://www.sqlservercentral.com/columnists/awarren/

It does work, but can't say its very elegant for grouping/packaging!

Andy

http://www.sqlservercentral.com/columnists/awarren/

Cant think of any permissions required. SQL manages the files, as long as you can get a connection to the box and authenticate with SQL, EM should work.

Andy

http://www.sqlservercentral.com/columnists/awarren/

One of these days we'll have to get this written down exactly! Chris, you dont need AWE to use up to the 3G mark, correct? If you use /3GB in...

You can do it with Exec(). Downsides are you dont get a compiled query plan, security is evaluated at run time, presents a potential security flaw via an injection attack....

Not aware of any issues. Recommend you start a new topic, we'll see if anyone has ideas.

Andy

http://www.sqlservercentral.com/columnists/awarren/

By profiling I mean running SQL Profiler to see exactly what sql is being sent from the client machine. Thats how I got the text I posted earlier showing what...