You can't do that with that little stored information - you need a piece of common information to relate the two rows worth of information together. For example:
SELECT a.*, b.* FROM Table1 a, Table2 b
Will work - sort of - but it probably won't produce anything you actually wanted because SQL is at liberty to return things in any order it wants, so it returns all combinations of all rows. So if Table1 has three rows:
1 AAA 2013-04-11 00:00:00.000
2 AAB 2013-03-01 00:00:00.000
3 AAC 2013-03-06 00:00:00.000
And Table 2 has four rows:
10 522 2013-03-06 00:00:00.000
20 584 2013-03-06 00:00:00.000
30 584 2013-03-06 00:00:00.000
40 584 2013-03-06 00:00:00.000
Then the above query will give you 12 rows:
1 AAA 2013-04-11 00:00:00.000 10 522 2013-03-06 00:00:00.000
1 AAA 2013-04-11 00:00:00.000 20 584 2013-03-06 00:00:00.000
1 AAA 2013-04-11 00:00:00.000 30 584 2013-03-06 00:00:00.000
1 AAA 2013-04-11 00:00:00.000 40 584 2013-03-06 00:00:00.000
2 AAB 2013-03-01 00:00:00.000 10 522 2013-03-06 00:00:00.000
2 AAB 2013-03-01 00:00:00.000 20 584 2013-03-06 00:00:00.000
2 AAB 2013-03-01 00:00:00.000 30 584 2013-03-06 00:00:00.000
2 AAB 2013-03-01 00:00:00.000 40 584 2013-03-06 00:00:00.000
3 AAC 2013-03-06 00:00:00.000 10 522 2013-03-06 00:00:00.000
3 AAC 2013-03-06 00:00:00.000 20 584 2013-03-06 00:00:00.000
3 AAC 2013-03-06 00:00:00.000 30 584 2013-03-06 00:00:00.000
3 AAC 2013-03-06 00:00:00.000 40 584 2013-03-06 00:00:00.000
What you want is some common data, so row a of Table1 is associated only with row d of Table2.