Store logging in separate or existing database? In a .NET WebForms project we want to log certain actions in a database for a year. The estimate is that the log will have a maximum size of 1GB (20.000 records per day of 10 fields) that will probably be queried a maximum times of 2 per day.

We are discussing if it is advisable to put the logging table in a new database (on perhaps even a separate server), or use a new table in our existing database. 

The advantages of using our existing database are that we do not need to make a new connection in the code nor administrate a new database. The disadvantage might be that the database cannot handle it.

What are your insights? Do you have any advice?
I would go for the same database, for the reasons you state in your question. If you're worried about performance or growth, create a new "logging" filegroup and put the logging table(s) on that. If things grow out of hand in the future, you can move the .ndf (the physical file that contains the new filegroup) to a different physical drive.

Even if you stick to the same server and add a new database, the effect is similar. You don't have to create a new connection in your client application - all you have to do is reference the table by a three-part name, [database].[schema].[table].

Edit: also, consider if the logged information should "follow" the rest of the database, or if it's specific to a certain server or environment.